Last week I sent an e-mail to the dita-users list, asking the larger community for feedback about the proposed <mapresources> element. (You can read my e-mail to the list below.) Seven people responded: Radu Coravu, Syncrosoft Leigh White, IXIASOFT Megan Bock, Netapp (?) Julio Vasquez Mark Schubert, parson Reece Roggentien
chrispitude@gmail.com With one exception, responders wanted to make <mapresources> available in map. Here are some excerpts from the e-mails: I applaud this idea! I think the distinction between maps referenced by mapresources and those referenced the usual way is an important one. I d prefer for it to be available in both bookmap and map. We have some outputs that have map root documents rather than bookmap. Definitely long overdue. I've always struggled with where to place the objects mentioned and having an element to gather cover image references, keydefs, and warehouse topics so it was clear that these are just non-content objects is a great add. Thanks. I d certainly use it in the map element. We use plenty of keys and have content used specifically for cover pages, and it would be helpful to be able to group them under a dedicated organizing element. In lieu of such an element, we ve implemented guidelines for where keydefs should be placed in relation to topicrefs and maprefs. It will provide a solution for the following issue:
https://www.oxygenxml.com/forum/post54203.html The one person concerned about making <mapresources> available in map was Radu Coravu, who commented I clearly see the benefit for it in a bookmap, as now we need to place all those key definitions in the frontmatter. But maybe for a plain DITA <map> it might not make that much sense, it would increase the complexity of the choices you need to make when you want to add a new element on the first level of the DITA Map. He suggested constraining map to limit the places that <mapresources> is permitted. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting
www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) -------- Forwarded Message -------- Subject: [dita-users] New DITA element: Request for feedback Date: Thu, 3 Oct 2019 08:03:24 -0400 From: Kristen James Eberlein
kris@eberleinconsulting.com [dita-users] <
dita-users@yahoogroups.com> Reply-To:
dita-users@yahoogroups.com To: dita-users <
dita-users@yahoogroups.com> I'd like to ask the larger DITA community for feedback. (Skip ahead and look for bold highlighting if you want to jump ahead to my question.) The DITA TC will be updating book map for DITA 2.0. One of the changes will be adding a new element (<mapresources>) that will serve as a location for resource-only objects like the following: Key definitions Subject schemes Topics that contain content only used in processing, for example, information used to generate a PDF cover page The DITA TC is considering the best way to implement this change. We are considering two options: Define <mapresources> as part of bookmap Add <mapresources> to the map group domain. This would make the new element available everywhere that <topicref> elements are allowed. Question for the community: Would you find <mapresources> useful in map? Or would it just be another element that your map authors would be distracted/inconvenienced by? The following code sample illustrates how the new element will be used in bookmap: <?xml version= 1.0 encoding= UTF-8 ?> <!DOCTYPE bookmap PUBLIC -//OASIS//DTD DITA 2.0 BookMap//EN bookmap.dtd > <bookmap> <booktitle> <mainbooktitle>Test bookmap</mainbooktitle> </booktitle> <mapresources> <mapref href= subject-scheme.ditamap type= subjectscheme /> <topicref href= moz-signature >-- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting
www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) __._,_.___ Posted by: Kristen James Eberlein <
kris@eberleinconsulting.com> Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (1) Visit Your Group Privacy Unsubscribe Terms of Use . __,_._,___