About: notation

This page provides a structured representation (serialized as HTML+RDFa) of the description of the entity denoted ("referred to") by the hyperlink that anchors the About: <Entity Label> text at the top.

The data is presented here in the form of a collection of Entity->Attribute->Value (EAV) or Subject->Predicate->Object (SPO) relations.

In conformance with core Web Architecture, the same description data may also be retrieved in a variety of other negotiable serialization formats, which currently include CSV, HTML+Microdata, (X)HTML+RDFa, N-Triples, Turtle, N3, RDF/JSON, JSON-LD, RDF/XML, Atom, and CXML.

Why is this page important?

This page and its neighbors provide 5-Star Linked Data URIs (Web Super Keys) for HTTP-accessible data. These URIs are powerful starting points for serendipitous data discovery using the Web's "follow your nose" pattern, as well as a key ingredient for SPARQL queries over HTTP, ODBC, JDBC, ADO.NET, OLE-DB, or XMLA connections.

A single link from this page can be the seed of a powerful Web traversal, en route to discovery and exploitation of unimagined insights, using existing tools such as browsers, spreadsheets, business intelligence and analytics packages, basic report writers, presentation generators, project management packages, and many others.

How can I discover more structured data like this?

A variety of discovery pointers are available to users and user agents (software programs) that include:

<link /> relations embedded within the <head /> section of each description page
"Link:" response headers included as part of HTTP response metadata.

Can I expose my own Web resources this way?

Yes! Simply include entries, based on the example below, in the <head/> section of your (X)HTML page, whether static or dynamically generated --

<link rel="related"
    title="My Data in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/<scheme-part-of-url>/<host-part-of-url>/<path-part-of-url>"
    />

The scheme part is the first bit of a URI, up to but not including the first colon (":"). The host part includes the port, if any, and is found between the double solidus ("//") following the first colon, and the first solidus ("/") thereafter. The path part is everything thereafter (possibly including a query part or fragment identifier part).

For example, if your original page were at --

http://en.wikipedia.org/wiki/Linked_Data

-- the scheme part is "http", the host part is "en.wikipedia.org", and the path part is "wiki/Linked_Data". You could therefore provide access to a Linked Data graph rendition by including a <head/> entry like this --

<link
    rel="related"
    title="Linked data - Wikipedia, the free encyclopedia - in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/http/en.wikipedia.org/wiki/Linked_Data"
    />

Additional Information

URIBurner.com -- a live service that produces pages like this
OpenLink Data Explorer (ODE) -- a browser plug-in that enables you to browse and bookmark Linked Data pages via additions to the browser menus, both main and contextual
- ODE usage examples

Sponging disallowed (Read-only view)

By convention, skos:notation is used with a typed literal in the object position of the triple.

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	DatatypePropertyhttp://www.w3.org/2002/07/owl#DatatypeProperty
comment	By convention, skos:notation is used with a typed literal in the object position of the triple. (en)
isDefinedBy	SKOS Core Vocabularyhttp://www.w3.org/2008/05/skos
label	notation (en)
described by	proxy:entity/http/www.w3.org/2008/05/skoshttp://ods-qa.openlinksw.com:8896/about/id/entity/http/www.w3.org/2008/05/skos
definition	A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme. (en)
Date Issued	2008-05-xx
change note	Initial description.nodeID://b601296 Initial description.nodeID://b601328 Initial description.nodeID://b601360 Initial description.nodeID://b601392 Initial description.nodeID://b604329 Initial description.nodeID://b604361 Initial description.nodeID://b604393 Initial description.nodeID://b604425 Initial description.nodeID://b613097 Initial description.nodeID://b613129 Initial description.nodeID://b613161 Initial description.nodeID://b613193 Initial description.nodeID://b613225 Initial description.nodeID://b613257 Initial description.nodeID://b613289 Initial description.nodeID://b613321 Initial description.nodeID://b613353 Initial description.nodeID://b613385 Initial description.nodeID://b613417 Initial description.nodeID://b613449 Initial description.nodeID://b613481 Initial description.nodeID://b613513 Initial description.nodeID://b613545 Initial description.nodeID://b613577 Initial description.nodeID://b613609 Initial description.nodeID://b613641 Initial description.nodeID://b613673 Initial description.nodeID://b613705 Initial description.nodeID://b1151178 Initial description.nodeID://b1151210 Initial description.nodeID://b1179474 Initial description.nodeID://b1179506 Initial description.nodeID://b1222555 Initial description.nodeID://b1222587 Initial description.nodeID://b1306324 Initial description.nodeID://b1306356 Initial description.nodeID://b1363727 Initial description.nodeID://b1363759 Initial description.nodeID://b1423569 Initial description.nodeID://b1423602 Initial description.nodeID://b1479554 Initial description.nodeID://b1554539 Initial description.nodeID://b1554571 Initial description.nodeID://b1817690 Initial description.nodeID://b1817722

Property	Value
topic	SKOS Core Vocabularyhttp://www.w3.org/2008/05/skos
about	proxy:entity/http/www.w3.org/2008/05/skoshttp://ods-qa.openlinksw.com:8896/about/id/entity/http/www.w3.org/2008/05/skos