Skip to content

Suggested ordering of predicates on a conversion:Enhancement

timrdf edited this page Feb 13, 2011 · 62 revisions

Although order does not matter for the predicates on a conversion:Enhancement, the following order is suggested to align with the order in which they affect the triple asserted. Note that this is FULLY conceptual; order of enhancement specification (and application) is irrelevant. This order could be used when designing a GUI for constructing the enhancement parameters.

The namespace for the conversion vocabulary is http://purl.org/twc/vocab/conversion/.


  • ov:csvCol - referencing the column that this enhancement affects.
  • conversion:property_name - an alternative way to reference the column via its resulting predicate's local name. NOTE: not implemented.

  • ov:csvHeader - PURELY an (OWL) annotation property; a "poor-man's provenance" from the CSV header to aid identification between the original data file, the enhancements modifying it, and its resulting instance data.


  • conversion:equivalent_property - used to specify an external URI for this column, without the local-external redundancy of subproperty_of.
  • conversion:label - will become the rdfs:label of the predicate created for the triples instantiated by the current column.
  • conversion:comment - will become the rdfs:comment of the predicate created for the triples instantiated by the current column.
  • conversion:subproperty_of - identities additional predicates to use for the triples instantiated by the current column.



Notes

conversion:includes should be placed in the position corresponding to the types of enhancements it is including. For example, if it is including conversion:symbol/conversion:interpretation pairs, place it at the position that conversion:interpret would go.

Clone this wiki locally