The RDF graph identifier (URI) of the local schema, and the subgraph identifier of the source schema (i.e., i and j) are also stored in the record, whereas the actual schema are stored in the schema repository.
For example, querying a gene for homologues uses the gene's stable Ensembl identifier to query the Compara schema, and the target 'hits' retrieved contain enough information to convert them to Core schema objects if required (target stable id, chromosome name and coordinates, and target species name).
This commercial repository is not currently OAI-PMH/OAI-ORE compliant and so no standard ORE or METS resource maps are declared to DataCite using e.g. the related identifier element of the DataCite metadata schema.
We report such a new naming schema as nucleotide universal identifier (nuID).
Using the relationships among different identifiers, we have optimized the database schema (Supplementary Figure S1) to improve the response time of the database when gene/protein expression, genomic mutation, PTM and PPI data are searched for.
The Querying process takes RDF and allows this to be queried using SPARQL, or to be converted back into XML using an XML schema annotated with CDE identifiers to define the output format.
id=<component id> /processors Get identifiers and input/output streams schemas of one or all the processors, possibly in extended form (logic, state, schemas).
Standardization is a process that takes data formatted in XML according to an XML schema that is annotated with CDE identifier and produces equivalent RDF for further processing, for example querying or inference.
id=<producer id>, sensor=<sensor id>, *sampling=<sampling rate> /storages Get identifiers, types and input/output schemas of one or all the storages.
