About: Plan execution

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)

Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	Classhttp://www.w3.org/2002/07/owl#Class
equivalentClass	nodeID://b722518nodeID://b722518 nodeID://b722611nodeID://b722611 nodeID://b722704nodeID://b722704 nodeID://b722797nodeID://b722797 nodeID://b737134nodeID://b737134 nodeID://b737227nodeID://b737227 nodeID://b737320nodeID://b737320 nodeID://b737413nodeID://b737413 nodeID://b839535nodeID://b839535 nodeID://b839628nodeID://b839628 nodeID://b839721nodeID://b839721 nodeID://b839814nodeID://b839814 nodeID://b846069nodeID://b846069 nodeID://b846162nodeID://b846162 nodeID://b846255nodeID://b846255 nodeID://b846348nodeID://b846348 nodeID://b847181nodeID://b847181 nodeID://b847274nodeID://b847274 nodeID://b847367nodeID://b847367 nodeID://b847460nodeID://b847460 nodeID://b862018nodeID://b862018 nodeID://b862111nodeID://b862111 nodeID://b862204nodeID://b862204 nodeID://b862297nodeID://b862297 nodeID://b872052nodeID://b872052 nodeID://b872145nodeID://b872145 nodeID://b872238nodeID://b872238 nodeID://b872331nodeID://b872331 nodeID://b873330nodeID://b873330 nodeID://b873423nodeID://b873423 nodeID://b873516nodeID://b873516 nodeID://b873609nodeID://b873609 nodeID://b892590nodeID://b892590 nodeID://b892683nodeID://b892683 nodeID://b892776nodeID://b892776 nodeID://b892869nodeID://b892869 nodeID://b895126nodeID://b895126 nodeID://b895219nodeID://b895219 nodeID://b895312nodeID://b895312 nodeID://b895405nodeID://b895405 nodeID://b1288941nodeID://b1288941 nodeID://b1289081nodeID://b1289081 nodeID://b1291564nodeID://b1291564 nodeID://b1291759nodeID://b1291759 nodeID://b1295840nodeID://b1295840 nodeID://b1295980nodeID://b1295980 nodeID://b1314334nodeID://b1314334 nodeID://b1314474nodeID://b1314474 nodeID://b1323407nodeID://b1323407 nodeID://b1323547nodeID://b1323547 nodeID://b1348275nodeID://b1348275 nodeID://b1348415nodeID://b1348415 nodeID://b1348807nodeID://b1348807 nodeID://b1348947nodeID://b1348947 nodeID://b1362615nodeID://b1362615 nodeID://b1362755nodeID://b1362755 nodeID://b1440711nodeID://b1440711 nodeID://b1466932nodeID://b1466932 nodeID://b1467072nodeID://b1467072 nodeID://b1469355nodeID://b1469355 nodeID://b1472916nodeID://b1472916 nodeID://b1524038nodeID://b1524038 nodeID://b1524178nodeID://b1524178 nodeID://b1572621nodeID://b1572621 nodeID://b1572761nodeID://b1572761 nodeID://b1602534nodeID://b1602534 nodeID://b1602674nodeID://b1602674 nodeID://b1625454nodeID://b1625454 nodeID://b1664990nodeID://b1664990 nodeID://b1665130nodeID://b1665130 nodeID://b1728954nodeID://b1728954 nodeID://b1729094nodeID://b1729094
subClassOf	Situationhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Situation
comment	Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.
isDefinedBy	DOLCE+DnS Ultralitehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl
label	Esecuzione di piano (it) Plan execution (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

Property	Value
topic	DOLCE+DnS Ultralitehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl
about	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