Tim Berners-Lee:
- Use URIs as names for things
- Use HTTP URIs so that people can look up those names
- When someone looks up a URI, provide useful information, using the standards
- Include links to other URIs so that people can discover more things
LOD Request
- Http GET that results in a response formatted as RDF
- Response format can be determined by explicit URL as well as by content negotiation using accept headers.
- RDF browsers:
- Marbles (http://marbles.sourceforge.net/)
- Tabulator (http://www.w3.org/2005/ajar/tab)
Relationship to the Ontology
- “follow your nose”
- Graphs that can be navigated to find useful information without knowing the structure of the ontology
- Ontology terms in the returned data should be dereferenceable
- Linked data is not complete if the class and property definitions can’t be requested
Namespaces and VIVO LOD
- If VIVO is deployed at http://vivo.iu.edu
- Linked data requests for individuals are of the form http://vivo.iu.edu/individual/n123456
- Default namespace in deploy.properties should be http://vivo.iu.edu/individual
- Linked data requests for individuals are of the form http://vivo.iu.edu/individual/n123456
- A local ontology will be returned from
- http://vivo.iu.edu/ontology/ontName
- http://vivo.iu.edu/ontology/ontName/SomeClass
- http://vivo.iu.edu/ontology/ontName/SomeProperty
- The namespace for a local ontology would need to begin with http://vivo.iu.edu/ontology
Extended Linked Data
- Context nodes
- VIVO ontology is designed to represent historical information
- Not included in most prevalent linked-data models today
- authorships
- VIVO ontology is designed to represent historical information
- VIVO responds to LOD request with information about additional URIs beyond the one requested
Reference
http://www.w3.org/DesignIssues/LinkedData.html http://linkeddata.org