[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Potential stage one idea: split syntax diagrams from programming?
Iâm pretty sure I discussed this with the people a year or two ago, but it got dropped because itâs generally low priority. I was reminded of it while restarting work cleaning up the technical communications part of the spec.
Would it be useful to split the syntax diagram elements out of the programming domain? The elements are not widely used â I know a couple of companies use them heavily but for most authors, theyâre never touched.
My suggestion was to split syntax diagram elements into their own domain. The advantage is that for those who do not use syntax diagrams at all â but are still interested in other elements from the programming domain â it becomes easy to drop 15 elements by removing one domain. Basically, weâd continue to ship the markup unchanged and the OASIS shells would still integrate the domain (so there is no content migration). The 15 affected elements would get new domain tokens. The cost would be a search/replace of domain tokens in any processors, and â for those who use custom shells and want to keep syntax diagrams â adding the new domain into their DITA 2.0 based grammar shells.
The full list of elements that would be moved, with links to the 1.3 spec, is:
Does that sound useful, unnecessary, or too late to consider?