About: parthood

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)

A special kind of Situation that allows to include time indexing for the hasPart relation in situations. For example, if a Situation s 'finally, my bike has a luggage rack' isSettingFor the entity 'my bike' and the TimeIntervals 'now', or more specifically '29March2021', we need to have a time-index the part relation. With Parthood, we use includesWhole and includesPart properties. This can be done similarly for other arguments of parthood, e.g. location, configuration, topology, etc. Concerning the possible property characteristics reused from mereology (transitivity, asymmetry, reflexivity), they need to be implemented by means of rules (or, in a limited way, property chains using the binary hasPart or hasProperPart properties). A key is also added to ensure identification constraints of time-indexed parthood.

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	Classhttp://www.w3.org/2002/07/owl#Class
subClassOf	http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#TimeIndexedRelationhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#TimeIndexedRelation nodeID://b1288932nodeID://b1288932 nodeID://b1288933nodeID://b1288933 nodeID://b1289072nodeID://b1289072 nodeID://b1289073nodeID://b1289073 nodeID://b1291555nodeID://b1291555 nodeID://b1291556nodeID://b1291556 nodeID://b1291750nodeID://b1291750 nodeID://b1291751nodeID://b1291751 nodeID://b1295831nodeID://b1295831 nodeID://b1295832nodeID://b1295832 nodeID://b1295971nodeID://b1295971 nodeID://b1295972nodeID://b1295972 nodeID://b1314325nodeID://b1314325 nodeID://b1314326nodeID://b1314326 nodeID://b1314465nodeID://b1314465 nodeID://b1314466nodeID://b1314466 nodeID://b1323398nodeID://b1323398 nodeID://b1323399nodeID://b1323399 nodeID://b1323538nodeID://b1323538 nodeID://b1323539nodeID://b1323539 nodeID://b1348266nodeID://b1348266 nodeID://b1348267nodeID://b1348267 nodeID://b1348406nodeID://b1348406 nodeID://b1348407nodeID://b1348407 nodeID://b1348798nodeID://b1348798 nodeID://b1348799nodeID://b1348799 nodeID://b1348938nodeID://b1348938 nodeID://b1348939nodeID://b1348939 nodeID://b1362606nodeID://b1362606 nodeID://b1362607nodeID://b1362607 nodeID://b1362746nodeID://b1362746 nodeID://b1362747nodeID://b1362747 nodeID://b1440702nodeID://b1440702 nodeID://b1440703nodeID://b1440703 nodeID://b1466923nodeID://b1466923 nodeID://b1466924nodeID://b1466924 nodeID://b1467063nodeID://b1467063 nodeID://b1467064nodeID://b1467064 nodeID://b1469346nodeID://b1469346 nodeID://b1469347nodeID://b1469347 nodeID://b1472907nodeID://b1472907 nodeID://b1472908nodeID://b1472908 nodeID://b1524029nodeID://b1524029 nodeID://b1524030nodeID://b1524030 nodeID://b1524169nodeID://b1524169 nodeID://b1524170nodeID://b1524170 nodeID://b1572612nodeID://b1572612 nodeID://b1572613nodeID://b1572613 nodeID://b1572752nodeID://b1572752 nodeID://b1572753nodeID://b1572753 nodeID://b1602525nodeID://b1602525 nodeID://b1602526nodeID://b1602526 nodeID://b1602665nodeID://b1602665 nodeID://b1602666nodeID://b1602666 nodeID://b1625445nodeID://b1625445 nodeID://b1625446nodeID://b1625446 nodeID://b1664981nodeID://b1664981 nodeID://b1664982nodeID://b1664982 nodeID://b1665121nodeID://b1665121 nodeID://b1665122nodeID://b1665122 nodeID://b1728945nodeID://b1728945 nodeID://b1728946nodeID://b1728946 nodeID://b1729085nodeID://b1729085 nodeID://b1729086nodeID://b1729086
comment	A special kind of Situation that allows to include time indexing for the hasPart relation in situations. For example, if a Situation s 'finally, my bike has a luggage rack' isSettingFor the entity 'my bike' and the TimeIntervals 'now', or more specifically '29March2021', we need to have a time-index the part relation. With Parthood, we use includesWhole and includesPart properties. This can be done similarly for other arguments of parthood, e.g. location, configuration, topology, etc. Concerning the possible property characteristics reused from mereology (transitivity, asymmetry, reflexivity), they need to be implemented by means of rules (or, in a limited way, property chains using the binary hasPart or hasProperPart properties). A key is also added to ensure identification constraints of time-indexed parthood.
label	parthood (en)
described by	proxy:entity/http/www.ontologydesignpatterns.org/ont/dul/DUL.owlhttp://ods-qa.openlinksw.com:8896/about/id/entity/http/www.ontologydesignpatterns.org/ont/dul/DUL.owl
Creator	Aldo Gangemi
Date	2021-04-03 13:53:57Z (xsd:dateTime) http://www.w3.org/2001/XMLSchema#dateTime
hasKey	nodeID://b1288929nodeID://b1288929 nodeID://b1289069nodeID://b1289069 nodeID://b1291552nodeID://b1291552 nodeID://b1291747nodeID://b1291747 nodeID://b1295828nodeID://b1295828 nodeID://b1295968nodeID://b1295968 nodeID://b1314322nodeID://b1314322 nodeID://b1314462nodeID://b1314462 nodeID://b1323395nodeID://b1323395 nodeID://b1323535nodeID://b1323535 nodeID://b1348263nodeID://b1348263 nodeID://b1348403nodeID://b1348403 nodeID://b1348795nodeID://b1348795 nodeID://b1348935nodeID://b1348935 nodeID://b1362603nodeID://b1362603 nodeID://b1362743nodeID://b1362743 nodeID://b1440699nodeID://b1440699 nodeID://b1466920nodeID://b1466920 nodeID://b1467060nodeID://b1467060 nodeID://b1469343nodeID://b1469343 nodeID://b1472904nodeID://b1472904 nodeID://b1524026nodeID://b1524026 nodeID://b1524166nodeID://b1524166 nodeID://b1572609nodeID://b1572609 nodeID://b1572749nodeID://b1572749 nodeID://b1602522nodeID://b1602522 nodeID://b1602662nodeID://b1602662 nodeID://b1625442nodeID://b1625442 nodeID://b1664978nodeID://b1664978 nodeID://b1665118nodeID://b1665118 nodeID://b1728942nodeID://b1728942 nodeID://b1729082nodeID://b1729082

Property	Value
topic	DOLCE+DnS Ultralitehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl