Not logged in.
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.
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.
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.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" />
The superclass of all classes describing products or services types, either by nature or purpose. Examples for such subclasses are "TV set", "vacuum cleaner", etc. An instance of this class can be either an actual product or service or a placeholder instance for unknown instances of a mass-produced commodity. Since eClassOWL and other large products and services ontologies are used for both describing product and services instances and product and service makes and models, this top-level concept is the union of (1) Actual Product or Service Instances, (2) Product or Service Models, and (3) ProductOrServiceSomeInstances Placeholders. The latter are "dummy" instances representing anonymous products or services instances (i.e., such that are said to exist but not actually being exposed on the Web). See the GoodRelations Technical Report for more details on this. Examples: a) MyCellphone123, i.e. my personal, tangible cell phone b) Siemens1234, i.e. the Siemens cell phone make and model 1234 c) dummyCellPhone123 as a placeholder for actual instances of a certain kind of cell phones.
Property | Value |
---|---|
Type |
|
label |
|
isDefinedBy |
|
comment |
|
disjointWith |
|
described by |
|
Property | Value |
---|---|
subClassOf |
|
equivalentClass |
|
first |
|
domain |
|
range |
|
disjointWith |
|
topic |
|