User:Ilya/Registry: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
| Line 11: | Line 11: | ||
*Data is represented by a graph of triples (statements about resources) | *Data is represented by a graph of triples (statements about resources) | ||
*Syntax doesn't matter: there are many ways to serialize the data (XML, N3, etc). | *Syntax doesn't matter: there are many ways to serialize the data (XML, N3, etc). | ||
*Taxonomy vs ontology? | |||
==From XML to RDF== | ==From XML to RDF== | ||
(from [http://dx.doi.org/10.1038/nbt1139]) | (from [http://dx.doi.org/10.1038/nbt1139]) | ||
Revision as of 15:18, 6 February 2006
Data or Metadata
(from LSID best practices) Data is defined as a sequence of unchanging bytes. Examples of data are microscope images, a protein sequence, a text file, etc. Metadata is usually information that describes the data either literally (date created, MD5 check sum, size) or contains information describing the relationship between the data and other objects. If you cannot determine what should be data and what should be metadata from your data model, follow this rule of thumb: Large byte sequences are easier to manipulate as data, while short byte sequences can be included as data, metadata, or made available in both forms.
Miscellaneous
- Use LSID for parts identification
- Software agent can search distributed registries using an ontology. This is impossible right now because storage schema is unknown.
- What about sequence features?
- Part has features and has a sequence
- Sequence has features but part already has sequence
- Data is represented by a graph of triples (statements about resources)
- Syntax doesn't matter: there are many ways to serialize the data (XML, N3, etc).
- Taxonomy vs ontology?
From XML to RDF
(from [1])
