]> LSRN Schema Descriptions This vocabulary defines terms used to describe Life Science Record Name (LSRN) Schemas and related metadata. LSRN Schema defines a prefix (e.g. GO:), the format of the prefix-dependent record identifier, and the associated metadata. This vocabulary is based on Gene Ontology Consortium's GO.xrf_abbs file format. Alterations were made to clarify ambiguous properies and make the format more suitable for automatic processing by LSRN resolver. This vocabulary's metadata and format are based upon those of the FRBR-core vocabulary by Richard Newman and Ian Davis, available under CC license. The same license type is used to license this work. &vocabid; Sergei Egorov <esl@ariadnegenomics.com> Copyright © 2006 Sergei Egorov GO.xrf_abbs Copyright © 1999-2006 the Gene Ontology Consortium OWL metadata&format Copyright © 2005 Richard Newman and Ian Davis &lsrs; lsrs text/html HTML application/rdf+xml RDF 2006-02-12 LSRN Schema A schema for Life Science Record Names. A member of this class describes the subject of a record, format of its name (prefix and prefix-dependent part), and its mapping to other identifiers and locators (URIs, URLs). Members of this class should have unique URIs in &lsrr; namespace; their RDF identifiers serve as LSRN prefixes (e.g. &lsrr;GO defines the GO: prefix and GO schema). &lsrr; 1 1 1 1 1 1 2006-02-12 source database The name of the database storing the record, e.g. 'Gene Ontology'. 2006-02-12 database URL Web address of the database storing the record. This should be a link to the database's home page or some other good starting point for exploration of the database's metadata and content. 2006-02-12 primary subject of db record Primary subject of database record, e.g. 'gene'. In the future, this property will be accompanied by a reference to a term from a suitable ontology of common subjects of life science database records. To simplify the transition, please try to use one of the existing values before inventing your own. 2006-02-12 secondary subject of db record Secondary subject of database record, e.g. 'genetic disorders'. In the future, this property will be accompanied by a reference to a term from a suitable ontology of common subjects of life science database records. To simplify the transition, please try to use one of the existing values before inventing your own. 2006-02-12 type of a database ID ID type, e.g. 'sequential identifier' or 'accession number'. In the future, this property will be accompanied by a reference to a term from a suitable ontology of common maintenance models for database identifiers. To simplify the transition, please try to use one of the existing values before inventing your own. 2006-02-12 format of a database ID Free-text format description, e.g. 'positive numeral'. In the future, this property will be accompanied by a reference to a term from a suitable ontology of common syntaxes for database identifiers. To simplify the transition, please try to use one of the existing values before inventing your own. 2006-02-12 regexp for database ID POSIX-style extended regexp pattern for database IDs, e.g. '[A-Z][0-9]+'. This property should be a valid POSIX ERE (extended regular expression). It should be present if either redirect_to_ere or url_template_ere properties are specified. Group subexpressions ised in id_pattern_ere can be referred to via \1 .. \9 substitution patterns in the template properties. 2006-02-12 example of ID Example of database ID for the record (sans prefix). This property should be a real ID. Together with the corresponding id_example_subject, it is used to check the LSRN registry for dead links. 2006-02-12 subject of ID example Subject for the example ID. This property is used together with id_example to check the LSRN registry for dead links. For each URL template, a URL is produced by substituting id_example, and the resulting resource is retrieved and checked for literal presence of the id_example_subject string. 2006-02-12 redirect to prefix Another prefix to be used in place of the current one, e.g. 'INSD:'. This property is used by LSRN Resolver service to process alternative or common names and propose their canonical variants. The replacement LSRN is formed by appending the identifier part to the redirect_to_prefix property, which should end in colon. 2006-02-12 redirect via regexp A regexp template for replacement LSRN. This property should be a template used with id_pattern_ere regexp pattern. The template is copied, making substitutions according to the regexp match performed using id_pattern_ere. Each instance of '&' in template is replaced by the entire identifier. Each instance of '\n', where n is a digit between 1 and 9, is replaced by the substring corresponding to parenthesized group in id_pattern_ere. To get a literal '&' or '\n', prefix it in the template with '\'; to get a literal '\' preceding '&' or '\n', prefix it with another '\'. 2006-02-12 URL template prefix A URL prefix to form a complete URL. This property is used by LSRN Resolver to form a URL for the record. URLs are formed by appending the identifier part to each url_template_prefix property. 2006-02-12 URL template for ID regexp A regexp template to form a URL. This property is used by LSRN Resolver to form a URL for the record. The template is copied, making substitutions according to the regexp match performed using id_pattern_ere. Each instance of '&' in template is replaced by the entire identifier. Each instance of '\n', where n is a digit between 1 and 9, is replaced by the substring corresponding to parenthesized group in id_pattern_ere. To get a literal '&' or '\n', prefix it in the template with '\'; to get a literal '\' preceding '&' or '\n', prefix it with another '\'. 2006-02-12 NCBI db_xref key NCBI db_xref key for the schema, if different from schema prefix. This property is used to preserve the original NCBI's db_xref key if it contains characters which cannot be used in LSRN schema names. 2006-02-12 RNEF property name Ariadne Genomics RNEF property name for the schema. This property is used to facilitate mapping between LSRN schemas and an external ontology. 2006-02-12