Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for the data and data-about elements in the plugin #27

Open
ColinMaudry opened this issue Aug 9, 2014 · 0 comments
Open
Milestone

Comments

@ColinMaudry
Copy link
Owner

The data and data-about elements have semantics that are very close to what the RDF model enables:
http://docs.oasis-open.org/dita/v1.2/os/spec/langref/data.html#data
http://docs.oasis-open.org/dita/v1.2/os/spec/langref/data-about.html#data-about

Why not extracting them as rdf:Statement?

Ideal example:

DITA

<data name="subject" href="http://dbpedia.org/resource/Mexico"/>
<data-about href="http://dbpedia.org/resource/Mexico">
    <data name="population" value="115296767" datatype="http://www.w3.org/2001/XMLSchema#integer"/>
</data-about>

RDF (Turtle syntax)

<http://data.example.com/resources/map/en-us/d5e5/data:1;5:48>
    a rdf:Statement ;
    rdf:subject <http://data.example.com/resources/map/en-us/d5e5> ;
    rdf:predicate <http://data.example.com/resources/predicate/subject> ;
    rdf:object <http://dbpedia.org/resource/Mexico> .
<http://dbpedia.org/resource/Mexico>
    <http://data.example.com/resources/predicate/population> "115296767"^^xsd:integer .

Now, it's probable user will nest elements in various ways... I'm not sure yet how to handle that.

If the <data> element is specialized then the name of the element is used instead of @name.

@ColinMaudry ColinMaudry added this to the 1.0 milestone Aug 9, 2014
@ColinMaudry ColinMaudry changed the title Add support for the data and data-about in the plugin Add support for the data and data-about elements in the plugin Aug 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant