[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] "The DITA iceberg" presentation at DITA Europe 2016 -- how RNG focus could help
Point #5 above is the one that most closely relates to the iceberg problem. If base DITA with no domains is too much for you, today there are practical limits to what you can cut away, and still Follow The Rules. With RNG, that practical limit goes away. There's now a straightforward, easy to follow pattern for any constraint. At least, that is my understanding, and the basis for this entire note.
One outcome from this could be for DITA 2.0 to get away from modular DTDs and XSDs entirely, but keep our rules / instructions for modular RNGs.
There are reasons not to push everybody to RNG as their "source", but I'm wondering if the advantages outweigh the objections.
The following list of objections is probably not be exhaustive, but they're sure to come up:
I'm curious to hear what others would think about this. If the logic doesn't make sense, I'll blame jetlag, having returned last night from Munich. As mentioned, I've been thinking about this for a while, so it's also possible I jumped over some logical step that I had wrestled with some weeks ago.
Kristen James Eberlein ---11/17/2016 02:46:17 AM---Maybe we can separate the pain points raised in Leigh's presentation and possible solutions: Pain p
From: Kristen James Eberlein <firstname.lastname@example.org>
To: Tom Magliery <email@example.com>, DITA TC <firstname.lastname@example.org>
Date: 11/17/2016 02:46 AM
Subject: Re: [dita] "The DITA iceberg" presentation at DITA Europe 2016
Sent by: <email@example.com>
Maybe we can separate the pain points raised in Leigh's presentation and possible solutions:
2. Many people don't understand that they can configure their own document-type shells; they think the start set of shells ARE DITA. If they know that they can configure shells, it still might be too troublesome to implement them. For example, a small company with a handful of writers using version control on the file system will have to install doctype plug-ins whenever they upgrade their authoring tool or DITA-OT instance.
3. Constraints are ridiculously time consuming to implement in DTDs. It's relatively simple to subset a domain -- but to remove base elements (for example, <pre>) requires constraining every element that can contain the base element. It's much easier in RNG. And it just doesn't really work in XSD.
2. We need to do more education about configuration.
3. Maybe we need to move to a model where we encourage folks to configure, specialize, and constrain in RNG -- keeping to all the rules driven by modularization -- but them convert the RNG to a monolithic DTD for use in production. Yes, this will limit ease of interchange, but ...
4. Drop support for XSD.
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
+1 919 682-2290; kriseberlein (skype)
On 11/16/2016 10:45 PM, Tom Magliery wrote:
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Kristen James Eberlein
Sent: Tuesday, November 15, 2016 11:19 PM
To: DITA TC
Subject: [dita] "The DITA iceberg" presentation at DITA Europe 2016
Attached is a PDF from a session done by Leigh White, IXIASOFT, at this
year's DITA Europe conference. (I'll follow up later with some
additional PDFs from other sessions.)
I'd like to ask TC members to read and consider it; I'm looking forward
to discussion on the list.
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php