[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] DITA 2.0 Proposal: Add <titlealts> to <map>
I like this idea. It sort of seems obvious in retrospect, like "why didn't we think of this when doing bookmap", instead of treating book map as if it were a completely unique situation.
Chris Nitchie ---03/30/2017 08:53:35 AM---We should allow <titlealts> inside <map> as well as <topic>. We should also add a zero-or-more <titl From: Chris Nitchie <chris.nitchie@oberontech.com> To: "dita@lists.oasis-open.org" <dita@lists.oasis-open.org> Date: 03/30/2017 08:53 AM Subject: [dita] DITA 2.0 Proposal: Add <titlealts> to <map> Sent by: <dita@lists.oasis-open.org> We should allow <titlealts> inside <map> as well as <topic>. We should also add a zero-or-more <titlealt> element that can be specialized for specific purposes, and consider making <navtitle> and <searchtitle> specializations of <titlealt>. In developing applications that leverage DITA, you very frequently need to ask the question, “what’s this document’s title?” It should be as simple as looking for the <title> element, or its specialization, at the top level of the file. However, this doesn’t work for bookmap, because its title element - <booktitle> - is actually a collection of pseudo-title elements specialized from <ph> - <mainbooktitle> and <booktitlealt>. So you have to write special-case code to handle BookMap, which is irksome. Even then, it won’t work for other <map> types that use a similar trick (like D4P PubMap). Adding <titlealts> to <map> solves it for new map types, like whatever we’re doing for BookMap 2.0. Chris |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]