About: has narrower

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)

Narrower concepts are typically rendered as children in a concept hierarchy (tree).

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	ObjectPropertyhttp://www.w3.org/2002/07/owl#ObjectProperty
subPropertyOf	narrower transitivehttp://www.w3.org/2008/05/skos#narrowerTransitive
inverseOf	has broaderhttp://www.w3.org/2008/05/skos#broader
comment	Narrower concepts are typically rendered as children in a concept hierarchy (tree). (en) By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources. (en)
isDefinedBy	SKOS Core Vocabularyhttp://www.w3.org/2008/05/skos
label	has narrower (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 concept that is more specific in meaning. (en)
Date Issued	2008-05-xx
change note	Initial description.nodeID://b601306 Initial description.nodeID://b601338 Initial description.nodeID://b601370 Initial description.nodeID://b601402 Initial description.nodeID://b604339 Initial description.nodeID://b604371 Initial description.nodeID://b604403 Initial description.nodeID://b604435 Initial description.nodeID://b613107 Initial description.nodeID://b613139 Initial description.nodeID://b613171 Initial description.nodeID://b613203 Initial description.nodeID://b613235 Initial description.nodeID://b613267 Initial description.nodeID://b613299 Initial description.nodeID://b613331 Initial description.nodeID://b613363 Initial description.nodeID://b613395 Initial description.nodeID://b613427 Initial description.nodeID://b613459 Initial description.nodeID://b613491 Initial description.nodeID://b613523 Initial description.nodeID://b613555 Initial description.nodeID://b613587 Initial description.nodeID://b613619 Initial description.nodeID://b613651 Initial description.nodeID://b613683 Initial description.nodeID://b613715 Initial description.nodeID://b1151188 Initial description.nodeID://b1151220 Initial description.nodeID://b1179484 Initial description.nodeID://b1179516 Initial description.nodeID://b1222565 Initial description.nodeID://b1222597 Initial description.nodeID://b1306334 Initial description.nodeID://b1306366 Initial description.nodeID://b1363737 Initial description.nodeID://b1363769 Initial description.nodeID://b1423579 Initial description.nodeID://b1423612 Initial description.nodeID://b1479564 Initial description.nodeID://b1554549 Initial description.nodeID://b1554581 Initial description.nodeID://b1817700 Initial description.nodeID://b1817732

Property	Value
subPropertyOf	narrower matchhttp://www.w3.org/2008/05/skos#narrowMatch
inverseOf	has broaderhttp://www.w3.org/2008/05/skos#broader
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