What is this page?

This page provides a structured representation (serialized as HTML+RDFa) of the description of a given Web-accessible resource, which resource is indicated (or denoted) by the Data Source hyperlink.

The data represented here is structured as Entity-Attribute-Value (EAV) graphs, and it may may be retrieved in a variety of other serialization formats via hyperlinks (URLs). Available serialization formats 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 starting points for SPARQL queries over HTTP, or SQL queries via ODBC, JDBC, ADO.NET, OLE-DB, and XMLA connections, with results spanning the entire Web.

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

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.

Is this related to the Linked Data meme?

Every link on this page resolves to a description-oriented document that's human and/or machine comprehensible.

This means that any and every Web document can be turned into a structured data container, which is then available for SPARQL and SQL queries via HTTP or "native" protocols.

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="alternate"
  title="My Data in RDF Linked Data form"
  type="<mime type>"
  href="http://linkeddata.uriburner.com/about/id/<URL-of-a-Web-Page>"
/>

For example, if your original page were at:
  http://en.wikipedia.org/wiki/Linked_Data
you could provide access to an EAV-based description serialized as Turtle/N3, by including a <head/> entry like this:

<link
  rel="alternate"
  title="Linked data - Wikipedia, the free encyclopedia - described as RDF (Turtle/N3 format)"
  type="text/n3"
  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
[OpenLink Software]

About: Using an Application Profile Based Service Registry

An Entity of Type : Thing, from Data Source : oai:dcmi.ischool.washington.edu:article/8, within Data Space : demo.openlinksw.com
QRcode image

  • References
  • Referenced By
Contributor
  • The Joint Information Systems Committee (JISC) of the UK Higher and Further Education Funding Councils
Coverage
  • nodeID://b512825
  • nodeID://b512826
  • nodeID://b512827
Creator
  • Ann Apps; The University of Manchester, UK
Date
  • 2007-08-29
Description
  • The JISC Information Environment Service Registry (IESR) aims to assist other applications, to discover and devolve materials that match their users’ interests in their research, learning and teaching. This paper describes the experience of using an application profile throughout the application development process, from initial data design, through application implementation, to scenarios illustrating application use. Also discussed is the benefit of using an application profile to share both a data schema and actual data with similar initiatives.
Format
  • application/pdf
Identifier
  • http://www.dcmipubs.org/ojs/index.php/pubs/article/view/8
Language
  • en
Publisher
  • Dublin Core Metadata Initiative
Rights
  • All intellectual property rights in papers submitted to the DCMI Proceedings reside with the authors. DCMI identifies the authors as the copyright holders unless specifically directed otherwise. DCMI requires non-exclusive permission from the authors published in the Proceedings to disseminate and make their works available in any form or medium. Authors are responsible for clearing any rights prior to submitting materials to the Proceedings.
Source
  • DCMI Proceedings; 2007; pp. 63-73
Subject
  • nodeID://b512822
  • nodeID://b512823
  • application profiles; interoperability; cross-domain processes; domain metadata; metadata harvesting; registries and registry services
Title
  • Using an Application Profile Based Service Registry
Type
  • nodeID://b512824
  • Peer-reviewed Paper
described by
  • oai:dcmi.ischool.washington.edu:article/8
Subject
  • oai:dcmi.ischool.washington.edu:article/8
container of
  • oai:dcmi.ischool.washington.edu:article/8
primary topic
  • oai:dcmi.ischool.washington.edu:article/8
Alternative Linked Data Views: Facets | PivotViewer | iSPARQL | ODE     Raw Linked Data formats: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD
This material is Open Knowledge   W3C Semantic Web Technology     This material is Open Knowledge Creative Commons License Valid XHTML + RDFa
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.
OpenLink Virtuoso version 06.03.3131, on Linux (x86_64-unknown-linux-gnu), Single Edition