]> RDF-in/RDF-out (RIRO) Service Descriptions This vocabulary defines terms used to describe RIRO services. A RIRO service is characterised by its connection point, its command name and description, its input pattern, and its output template. RIRO Service Description contains all the information needed to use the service. The description is built as a set of properties of the connection point resource (a node which URI is the URL of the service). Input patterns and output templates are described using the accompanying RDF Graph Patterns and Templates vocabulary (http://purl.org/vocab/riro/gpt). &vocabid; Sergei Egorov <esl@ariadnegenomics.com> Copyright © 2006 Sergei Egorov OWL metadata & format Copyright © 2005 Richard Newman and Ian Davis &sdl; sdl text/html HTML application/rdf+xml OWL 2006-03-05 RIRO Service A RDF-in/RDF-out (RIRO) Service. A member of this class is a service supporting the RIRO protocol. As a rule, a member of this class is assigned a URI; if so, the URI is interpreted as URL of the service's connection point. 1 1 1 1 1 1 1 1 1 1 2006-03-05 command name The name of the command to invoke the service. Please supply short and descriptive name, suitable for use in menus, command lists etc. Recommended length is 10-40 characters. Example: 'Resolve LSRN to Record, URLs'. This property is required. 2006-03-05 command description The description of the command to invoke the service. Please keep the description brief - no longer than 25-30 words. The description should be suitable for use in tooltips, help texts etc. 2006-03-05 file under The category/subcategory of the command to invoke the service. This property allows one to group related services together. The format of the property is category/subcategory/subsubcategory/..., similar to the convention used in the Open Directory Project (dmoz.org). Category names should follow the conventions for command names (10-40 characters, capitalized). Example: 'Related/Journal Articles' 2006-03-05 input pattern The pattern matching proper input graphs. Graph patterns should be expressed via the RDF Graph Patterns and Templates vocabulary (http://purl.org/vocab/riro/gpt). This property is required. 2006-03-06 output template The template for output graphs produced by the service. Graph patterns should be expressed via the RDF Graph Patterns and Templates vocabulary (http://purl.org/vocab/riro/gpt). The input pattern and output template can share blank nodes. In real calls, the query and the reply graph will also share corresponding blank nodes by reusing nodeIDs; the reply is considered to be in the same nodeID namespace as the query. This property is required. 2006-03-06 HTTP method Query method ('get' or 'post'). If the query method is 'get', the service is assumed to be idempotent (the query will have no side effects). This property is required. get post 2006-03-06