= !BluePrint: HXL = [[TOC]] == Introduction == [http://hxl.humanitarianresponse.info HXL] is a shared vocabulary for [http://linkeddata.org Linked Data] for the humanitarian domain. 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. Example: {{{#!xml hxl:IDP 127386 http://www.example.org/eden/org/organisation/2 hxl:Organisation Example Organisation }}} This example encodes the RDF statements: - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''is a'' rdf:type => ''Internally Displaced Population'' hxl:IDP - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''has a'' hxl:personCount => 127386 - ''The resource at'' {{{http://www.example.org/eden/dvr/population/823}}} => ''comes from'' hxl:source => http://www.example.org/eden/org/organisation/2 ...where the latter refers to the resource described in the next RDF statements: - ''The resource at'' {{{http://www.example.org/eden/org/organisation/2}}} => ''is a'' rdf:type => rdf:resource hxl:Organisation. - ''The resource at'' {{{http://www.example.org/eden/org/organisation/2}}} => ''has'' orgName => "Example Organisation". (Note that this RDF/XML example is only one possible notation) 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. 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. 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. == Stakeholders == - ''tbw'' == User Stories == - ''tbw'' == Requirements == - ''tbw'' === Functional === - ''tbw'' === Non-functional === - ''tbw'' === Interoperability === - ''tbw'' === Standards === - ''tbw'' === System Constraints === - ''tbw'' == Architecture == - ''tbw'' == Design == - ''tbw'' === Data Model === - ''tbw'' === Workflows === - ''tbw'' === Technologies === - ''tbw'' == Current Implementation == - ''tbw'' == Planned Implementation == - ''tbw'' == Future Extensions == - ''tbw'' == Outstanding Questions == - ''tbw'' == References == - ''tbw'' ---- BluePrint