Changes between Version 5 and Version 6 of CMD2RDF/sysarch


Ignore:
Timestamp:
05/21/14 19:16:48 (10 years ago)
Author:
xnrn@gmx.net
Comment:

added image sketching the literal2entity process

Legend:

Unmodified
Added
Removed
Modified

  • CMD2RDF/sysarch

    v5 v6  
    109109'''Note''': It is important to perform the lookup on aggregated data (`< data category, value >` pairs), otherwise introducing a huge inefficiency.
    110110
     111Following figure sketches the processing workflow for resolving literal values to entities using a external Vocabulary Service (CLAVAS?) (it originates from the thesis by Durco: ''SMC4LRT''):
     112
     113[[Image(SMC_CMD2LOD.png,80%,align=center)]]
     114
     115=== Modelling issues
     116
    111117In the RDF modelling of the CMD data, we foresee two predicates for every CMD-element, one holding the literal value (e.g. `cmd:hasPerson.OrganisationElementValue`) and one for the corresponding resolved entity (`cmd:hasPerson.OrganisationElementEntity`). The triple with literal value is generated during the basic `CMDRecord2RDF` transformation. The entity predicate has to be generated in a separate action, essentially during the lookup step.
    112118