Skip to content
This repository has been archived by the owner on May 25, 2020. It is now read-only.

new mechanism for RDF generation/import #15

Closed
kohlhase opened this issue Mar 17, 2015 · 2 comments
Closed

new mechanism for RDF generation/import #15

kohlhase opened this issue Mar 17, 2015 · 2 comments
Assignees

Comments

@kohlhase
Copy link
Member

We want to read RDF XML back in, that means we cannot use the templating engine to generate the XML. Instead we decorate

  • the <concept> element in a KannSpec with a rdftype="o:foo" attribute, this generates a RDF triple of the form <rdf:type rdf:resource="o:foo"/>.
  • the <field> element with a ```rdfpred="o:bar" attribute, this generates an RDF triple
    • <o:bar>baz</o:bar> if the type of the field is text
    • <o:bar rdf:resource="#ref#"/>, if the type of the field is reference and #ref# the value of the reference.
    • <o:bar>#val#</o:bar> if the type of the field is select and #val# is the value of the chosen option.
    • <o:bar rdf:resource="#obj#"/> if the type of the field is select and the chosen option carries an attribute rdfobj="#obj#".
      This should cover all the cases.
@kohlhase
Copy link
Member Author

I have already extended schema/kannspec.rnc accordingly an updated the KannSpecs omdoc-annotations.xml and olia.xml. The KannSpec stanford.xml was never complete, see #16

@tkw1536
Copy link
Member

tkw1536 commented Apr 24, 2015

@kohlhase I am almost done implementing the export. Because javascript has non-optimal handling of case-sensitive elements, it took a bit longer. While I was at it, I updated the export sample to pass the RDF validator at http://www.w3.org/RDF/Validator/ .

Note that this is only on the dev branch because @sourabhlal code isn't stable enough for a merge to master.

@tkw1536 tkw1536 closed this as completed Jul 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants