Changes between Version 3 and Version 4 of BluePrint/HXL


Ignore:
Timestamp:
01/29/14 23:16:34 (8 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/HXL

    v3 v4  
    3939(Note that this RDF/XML example is only one possible notation)
    4040
    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 extract/export the data into standard formats, e.g. DOC, KML, or XLS.
     41Typically, data-producing EM applications would export such a RDF/XML 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 extract/export the data into standard formats, e.g. DOC, KML, or XLS.
    4242
    4343The purpose of this BluePrint is to define the role of Eden as
     
    4848The most obvious role for Eden at this point is that of the HXL exporter.
    4949
    50 A proof-of-concept prototype XSLT template has been implemented for the project_activity resource.
    5150== Stakeholders ==
    5251
     
    8382== Architecture ==
    8483
    85   - ''tbw''
     84Again the example from the introduction:
     85
     86{{{#!xml
     87<?xml version="1.0"?>
     88<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     89         xmlns:hxl="http://hxl.humanitarianresponse.info/ns">
     90  <rdf:Description rdf:about="http://www.example.org/eden/dvr/population/823">
     91    <rdf:type>hxl:IDP</rdf:type>
     92    <hxl:personCount>127386</hxl:personCount>
     93    <hxl:source>http://www.example.org/eden/org/organisation/2</hxl:source>
     94  </rdf:Description>
     95  <rdf:Description rdf:about="http://www.example.org/eden/org/organisation/2">
     96    <rdf:type>hxl:Organisation</rdf:Type>
     97    <hxl:orgName>Example Organisation</hxl:orgName>
     98  </rdf:Description>
     99</rdf:RDF>
     100}}}
     101
     102Obviously, the structure of this example RDF/XML is very close to S3XML:
     103
     104{{{#!xml
     105<?xml version="1.0"?>
     106<s3xml>
     107  <resource name="dvr_population"
     108            url="http://www.example.org/eden/dvr/population/823">
     109      <data field="person_count">127386</data>
     110      <reference field="source_organisation_id"
     111                 resource="org_organisation"
     112                 uuid="urn:uuid:40391e28-4e8a-4021-bf29-a5dddd2e38f3"/>
     113  </resource>
     114  <resource name="org_organisation"
     115            uuid="urn:uuid:40391e28-4e8a-4021-bf29-a5dddd2e38f3"
     116            url="http://www.example.org/eden/org/organisation/2">
     117    <data field="name">Example Organisation</data>
     118  </resource>
     119</s3xml>
     120}}}
     121
     122...so that we should be able to use our in-line XSLT transformation capabilities to convert S3XML into HXL.
     123
     124A proof-of-concept XSLT template has been implemented for the project_activity resource.
    86125
    87126== Design ==