dita-lightweight-dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Fw: DITA template to RNG schema transform - release 0.1
- From: "Michael Priestley" <mpriestl@ca.ibm.com>
- To: dita-lightweight-dita@lists.oasis-open.org
- Date: Mon, 17 Oct 2016 13:16:07 -0400
Michael Priestley, Senior Technical Staff Member (STSM)
Enterprise Content Technology Strategist
mpriestl@ca.ibm.com
----- Forwarded by Michael
Priestley/Toronto/IBM on 10/17/2016 01:15 PM -----
From:
Tim Grantham <tim@precisioncontent.com>
To:
Michael Priestley/Toronto/IBM@IBMCA
Date:
10/17/2016 12:51 PM
Subject:
FW: DITA template
to RNG schema transform - release 0.1
Hi, Michael.
The list server is giving me grief again.
Can you please post it?
Thanks,
Tim.
_____________________________________________
From: Tim Grantham
Sent: Monday, October 17, 2016 12:47 PM
To: dita-lightweight-dita@lists.oasis-open.org
Subject: DITA template to RNG schema transform - release 0.1
Hi, everyone.
I have forward to Mark for posting to GitHub
files that include the first version of an XSLT stylesheet that converts
a lightweight DITA template topic to a RELAX-NG schema. The zip also includes
an example template topic, RNG versions of the lightweight DITA DTD (required
by the stylesheet), example output from the stylesheet (using the example
template as input), and an example topic that conforms to the RNG schema
generated from the example template.
For testing, the files should be extracted
to a single folder. You can use oXygen to run the transform on a template
or you can use Saxon to run the transform from a command line. If you want
to create and validate topics with an RNG schema, you will need an XML
editor, such as oXygen 18, that supports RNG schemas. If you need any assistance,
please let me know. If anyone wants to send me templates for testing, I’m
happy to do so.
Still to do:- Fix the integration of the highlight domain
into the generated RNG schema. Currently, the generated schema does not
allow highlight elements. This shouldn’t be hard to fix; I just ran out
of time.
- Fix the output when @specmodel=”choice”,
so that the content model for the base element gets inherited. Currently,
the new specialized child elements replace the base element’s content
model, rather than adding to it.
- Add support for the @importance attribute.
I’m fairly confident I can add this before the next meeting; it’s not
a lot of work.
- Split the output from the stylesheet into
two modules: topictype.rng and topictypeMod.rng.
- Consolidate the current LW DITA RNG files
into two files: topic.rng and topicMod.rng.
- Add jing-trang, a program that generates
DTDs and XSDs from RNG schemas.
- Eventually, incorporate the files into
a plugin for the Open Toolkit.
Otherwise, the stylesheet fully supports
the elements and attributes defined in the lightweight DTD, as they apply
to generating a schema.
The stylesheet should be tested with many
more templates, to expose errors in the LW DITA RNG schema and the XSLT
stylesheet. There are several places for errors to have crept into the
current work: - In the LW DITA DTD. The LW DITA RNG schema
is based on the LW DITA DTD, so errors in the DTD might have been unintentionally
incorporated into the RNG schema.
- In the LW DITA RNG schema. I might not
have correctly converted the LW DITA DTD to the RNG version. I corrected
some errors yesterday, but I may well have missed some.
- In the XSLT stylesheet. Errors could arise
from a misunderstanding of the requirements on my part, or errors in the
logic or design.
Regards,
Tim.
Tim Grantham
Director of Publishing Solutions
Precision Content Authoring Solutions Inc.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]