| 8 | Linked data use [http://en.wikipedia.org/wiki/Uniform_resource_identifier URI]s to identify data resources, and [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF] statements (triples) to describe their relationships. |
| 9 | |
| 10 | Example: |
| 11 | |
| 12 | {{{#!xml |
| 13 | <?xml version="1.0"?> |
| 14 | <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" |
| 15 | xmlns:hxl="http://hxl.humanitarianresponse.info/ns"> |
| 16 | <rdf:Description rdf:about="http://www.example.org/eden/dvr/population/823"> |
| 17 | <rdf:type>hxl:IDP</rdf:type> |
| 18 | <hxl:personCount>127386</hxl:personCount> |
| 19 | <hxl:source>http://www.example.org/eden/org/organisation/2</hxl:source> |
| 20 | </rdf:Description> |
| 21 | <rdf:Description rdf:about="http://www.example.org/eden/org/organisation/2"> |
| 22 | <rdf:type>hxl:Organisation</rdf:Type> |
| 23 | <hxl:orgName>Example Organisation</hxl:orgName> |
| 24 | </rdf:Description> |
| 25 | </rdf:RDF> |
| 26 | }}} |
| 27 | |
| 28 | This example encodes the RDF statements: |
| 29 | |
| 30 | - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''is a'' rdf:type => ''Internally Displaced Population'' hxl:IDP |
| 31 | - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''has a'' hxl:personCount => 127386 |
| 32 | - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''comes from'' hxl:source => http://www.example.org/eden/org/organisation/2 |
| 33 | |
| 34 | ...where the latter refers to the resource described in the next RDF statements: |
| 35 | |
| 36 | - ''The resource at'' {{{http://www.example.org/eden/org/organisation/2}}} => ''is a'' rdf:type => rdf:resource hxl:Organisation. |
| 37 | - ''The resource at'' {{{http://www.example.org/eden/org/organisation/2}}} => ''has'' orgName => "Example Organisation". |
| 38 | |
| 39 | (Note that this RDF/XML example is only one possible notation) |
| 40 | |
| 41 | Typically, data-producing EM applications would export such a description of their data resources to a common database (triple store), which can then be queried from consuming applications using standard APIs (e.g. RDF/SPARQL) and export the data into standard formats, e.g. DOC, KML, or XLS. |
| 42 | |
| 43 | The purpose of this BluePrint is to define the role of Eden as HXL exporting application, or as triple store with RDF/SPARQL API or as HXL consumer. |
| 44 | |
| 45 | The most obvious role for Eden at this point is that of the HXL exporter. A proof-of-concept prototype XSLT template has been implemented for the project_activity resource. |