search

kcl-ddh / kiln

Kiln is a multi-platform framework for building and deploying complex websites whose source content is primarily in XML. It brings together various independent software components into an integrated whole that provides the infrastructure and base functionality for such sites.
Apache License 2.0
34 stars 62 forks source link

Default RDF stylesheets are missing #4

Closed jmiguelv closed 10 years ago

jmiguelv commented 12 years ago

Add sample RDF stylesheets.

ajenhl commented 12 years ago

Do you mean sample XSLT to generate RDF/XML from TEI? That's going to be a tough one! Do we take this as an opportunity to push CIDOC CRM and FRBRoo? The GSR XSLT might prove an okay starting point in that case.

jmiguelv commented 12 years ago

Yes, I think we just need to add something simple as a guide on how to do it. Like with the Solr XSLTs. Pushing CIDOC-CRM is not a bad idea as well.

annajordanous commented 12 years ago

If it helps, we are working on TEI to RDF conversion for the SAWS project, in conjunction with Alan Stanley at UPEI. A TEI-Bare-to-RDF stylesheet is available at https://github.com/ajstanley/TEI_to_RDF.git . (NB these XSLTs are currently in active development).

We are working up from TEI-Bare (absolutely minimalist) to other customisations of TEI. Using Dublin Core as a base so far, but SAWS uses FRBRoo so I can see this tieing in well here.

We've also incorporated the recent changes on using the TEI element to encode RDF triples within TEI markup docs (SPO are @active, @ref, @passive, respectively).

Anna (CeRch)

PS would be very interested to see what you've come up with so far - can't find anything in our copy of kiln but I'm probably not looking in the right places

ajenhl commented 10 years ago

The tutorial includes a trivial TEI to RDF XSLT for use with the tutorial's TEI files. It doesn't use any established ontology, but does at least show how such an XSLT might look. I'm slightly averse, now, to include a 'pretend it's generic' TEI to RDF XSLT. We can get away with that for TEI to HTML, because HTML is (being used as) a presentation format, and it's relatively easy to map TEI elements to HTML equivalents, even though everyone will disagree about the specifics. With RDF, though, there is no common mapping, no common goals, etc, and I don't think we'd be doing anyone any favours (and increasing the maintenance burden) by including something more than an example of how to write such an XSLT, which the tutorial now provides.

Therefore, closing this issue; feel free to reopen if you have a convincing argument (and, preferably, patch!).