[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Concerns about issue #29 "Bookmap updates"
Hi Kris, Hi Kris, Just the glossref domain and map resources (new) domain are added. The ditavalref domain is already referenced in the bookmap DTD shell for DITA 1.3. Thereâs no way to add mapresources
domain to the bookmap otherwise without loosing control of the content model. As for glossref, the only other option is to add it topicref override, but then itâs available everywhere. I should be able to make to the meeting on Tuesday. The customer project that conflicted with the TC meeting time is wrapping up. Ãric Sirois DITA Toolsmithâ IXIASOFT 45 Chemin Bates, Suite 220 â Montreal, QC H2V 1A6 mobile + 1 647 462-3620 eric.sirois@ixiasoft.com
/
www.ixiasoft.com
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Kristen James Eberlein I have some concerns about the technical requirements for issue #29 "Bookmap updates". The TC approved the stage two proposal on 19 February 2019; I've taken over completing the stage three proposal from Eric Sirois, who is no longer a voting member. (Eric, we'd love to have you back when your schedule will let you attend TC meetings!) The technical requirements, as listed in the stage two proposal, create hard dependencies between the bookmap module and the following domains:
These dependencies are not something that the TC discussed, and until this point, the TC has not created document-type shells that have hard dependencies on domain modules. By a hard dependency, I mean that a document-type shell that DOES NOT contain these
domains will be broken. We need to talk about this. Is this what we wanted to do? Are there other ways to meet the user requirements without creating hard dependencies between the bookmap module and the various domains? I checked the DITA 1.3 bookmap shells that I have created for clients, and many of them DO NOT contain the DITAVALref and glossary reference domain -- --------------------------------------------------------------------- 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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]