26 November 2011 by Ian Davis
I’ve been mulling over this alternate way of thinking about RDF, one that is resource-oriented rather than triple-oriented. This is what I came up with:
The Resource Description Framework (RDF) is a framework for representing information in the Web. RDF has a simple data model that is easy for applications to process and manipulate. The data model is independent of any specific serialization syntax.
RDF provides information about resources through Resource Descriptions. A Resource Description consists of:
- A subject resource identified by a URI
- Zero or more relationships to other resources
- Zero or more properties having literal values
A relationship comprises a pair of URIs: the first URI denotes the type of relationship, the second identifies the related resource.
A property comprises a pairing of a URI with a literal value. The URI denotes the type of property. The literal value is a string with an optional datatype (denoted by a further URI) or language tag (as defined by RFC-3066)
Nothing technically different from the existing formulation (I omitted mention of blank nodes for brevity only – they would still be present) but perhaps a lot easier for developers used to resource-oriented systems to grok.
Note: in the original version of this post I used the term document-oriented, but switched to resource-oriented on the suggestion of Niklas Lindström
Note2: this formulation bears a striking resemblance to the HAL linking scheme for JSON