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

Implement Schematron schema generation from ODD #7

Open
ajenhl opened this issue Jul 26, 2012 · 3 comments
Open

Implement Schematron schema generation from ODD #7

ajenhl opened this issue Jul 26, 2012 · 3 comments
Assignees

Comments

@ajenhl
Copy link
Contributor

ajenhl commented Jul 26, 2012

kiln/sitemaps/odd.xmap has the beginnings of a set of pipelines for extracting Schematron schema files from an ODD file. The XSLT to implement this need to be written.

@ghost ghost assigned ajenhl Jul 26, 2012
@raffazizzi
Copy link

Hello,

really cool stuff, will look more into Kiln's use of ODD.

Just wondering if there's any way to use the TEI's Stylesheets?

http://tei.svn.sourceforge.net/viewvc/tei/trunk/Stylesheets/odds2/

Particularly extract-sch.xsl and extract-isosch.xsl for this specific case.

Best and great job!
Raffaele

On Thu, Jul 26, 2012 at 1:46 AM, Jamie Norrish <
reply@reply.github.com

wrote:

kiln/sitemaps/odd.xmap has the beginnings of a set of pipelines for
extracting Schematron schema files from an ODD file. The XSLT to implement
this need to be written.


Reply to this email directly or view it on GitHub:
#7

@ajenhl
Copy link
Contributor Author

ajenhl commented Jul 29, 2012

Thanks for the pointer to those XSLT, Raffaele - I'll certainly use extract-isosch.xsl as at least the basis for this work. My original thinking, that I'd appreciate feedback on, was to have two extractions of a schema from an ODD file: one built from the rules associated with the definition of the TEI, and the other built from the rules in an 'encoding guidelines' section of the ODD.

That seemed a useful distinction when I planned this work, since the schema in the second case would link to a transformed-for-display version of the guidelines, but I am now thinking it might be simplest just to use all of the rules at once. This wouldn't prevent a link to the encoding guidelines for those rules from that section, so there doesn't seem to be any downside.

@ajenhl
Copy link
Contributor Author

ajenhl commented Jun 18, 2013

d58ccde provides a much simplified form of the original intention, simply extracting all Schematron rules from an ODD file, and without yet linking to any documentation in that ODD. Such linking will probably wait until I have an actual example ODD containing project-specific encoding guidelines with associated Schematron rules, so I'm leaving this issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants