New

Draft/Review Space to migrate and exit from XML Schema (XSD) not supported by DITA 2.0

XML schema definition is not easy to maintain for Draft/Review Space.

Draft/Review Space requires the JSON files converted from XML Schema (XSD).  Possibly, larger part of the users may not choose XSD for DITA content DocType.  In that case, Relax NG (RNG) will be used for the source XML schema definition, and then that will be converted to RNG (and DTD), and finally converted to Draft/Review Space JSON files.  That conversion flow is not as smooth as expected.

Even though RNG is valid, output RNG (and DTD) may not work as expected.  Even though RNG was generated successfully without errors, Draft/Review Space JSON conversion may fail.  When that would happen, it might be needed to restart the flow from RNG edit and repeat the entire flow again and again.

My idea is to update Draft/Review Space directly dealing with native RNG (or DTD) without JSON conversion.  Then, that will be compatible with DITA 2.0, and also users can avoid the complicated workflow with XML schema.

Masayuki Yamane

  • DITA RNG support had begun by DITA 1.3.  So, DTD might be better than RNG in case DITA 1.2 support was needed.  However, I guess there isn't easy way to maintain DTD and XSD consistently in case of DITA 1.2, and I wonder using Draft/Review space with DITA 1.2 or older is realistic story.  Actually, our company was requested from RWS Professional Services to upgrade to DITA 1.3 when they introduce Draft/Review Space.

  • Thanks, Dave. Our company has an active voting member on the OASIS DITA TC. In the meantime, do you have any suggestions for how we can make the current process more efficient? We are going through a DTD change right now (constrained DTD), and while Collective Spaces is a prominent part of our TD environment, it's quite burdensome to keep it aligned with DTD updates.  

  • Allow me to backfill as there are a lot of angles to this idea...

    As we are all still on OASIS DITA 1.x, there are DTDs and XSDs delivered.

    The introduction of a new standard does not automatically remove the need across all customers for the old one. Without full replacement it just complicates it, remember https://xkcd.com/927/ :)

    One important piece is that we all expect the same or better performance. This is a very big risk to consider given that schema validation happens in all kinds of technology in-and-around the Tridion Docs platform ranging from xml editors, over DITA-OT to custom tooling or integrations with language partners.