After a long period of trying to demystify and unravel the
wonders of standards compliant structured data access, combined with
protocols (e.g., HTTP) that separate:
- Representation, and
I ended up with what I can best describe as the Data 3.0
Manifesto. A manifesto for standards complaint access to structured
data object (or entity) descriptors.
Some Related Work
Alex James (Program Manager Entity
Frameworks at Microsoft), put together something quite similar
to this via his Base4 blog (around the Web 2.0 bootstrap
time), sadly -- quoting Alex -- that post has gone where
discontinued blogs and their host platforms go (deep deep irony
It's also important to note that this manifesto is also a
variant of the TimBL's Linked Data Design Issues meme
re. Linked Data, but totally decoupled from RDF (data
representation formats aspect) and SPARQL which -- in my world view -- remain
Data 3.0 manifesto
- An "Entity" is the "Referent" of an "Identifier."
- An "Identifier" SHOULD provide a global, unambiguous, and
unchanging (though it MAY be opaque!) "Name" for its
- A "Referent" MAY have many "Identifiers" (Names), but each
"Identifier" MUST have only one "Referent".
- Structured Entity Descriptions SHOULD be based on the Entity-Attribute-Value (EAV) Data Model,
and SHOULD therefore take the form of one or more 3-tuples
(triples), each comprised of:
- an "Identifier" that names an "Entity" (i.e., Entity
- an "Identifier" that names an "Attribute" (i.e., Attribute
- an "Attribute Value", which may be an "Identifier" or a
- Structured Descriptions SHOULD be CARRIED by "Descriptor
Documents" (i.e., purpose specific documents where Entity
Identifiers, Attribute Identifiers, and Attribute Values are
clearly discernible by the document's intended consumers, e.g.,
humans or machines).
- Structured Descriptor Documents can contain (carry) several
Structured Entity Descriptions
- Stuctured Descriptor Documents SHOULD be network accessible via
network addresses (e.g., HTTP URLs when dealing with HTTP-based
- An Identifier SHOULD resolve (de-reference) to a Structured
Representation of the Referent's Structured Description.