[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] keyref attribute on non-titled non-linked container elements
If the Bookmap design allowed anything other than <bookmap> as the root of a <bookmap> map, it would be reasonable to have submaps rooted at <frontmatter>, <backmatter>, etc. and therefore reasonable to allow references from those topicrefs. However, because Bookmap does not allow for this, I think it's reasonable to disallow references from any topicref specialization that is fundamentally a grouping element and not intended to refer to a resource. Cheers, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 2/14/14, 8:24 AM, "Robert D Anderson" <robander@us.ibm.com> wrote: >Hi, > >Working through the attribute tables, I've so far encountered three >container elements in the BookMap specialization that use keyref. These >are explicitly non-titled, non-linking container elements: <frontmatter>, ><backmatter>, and <booklists>. These specialized elements explicitly >disallowed @navtitle (when there was no <navtitle> equivalent); they also >disallow @href because they are not intended to reference a topic. The >specialization left @keyref, but it's worth nothing this was DITA 1.1 >(keyref was still undefined). > >So the question is - what does @keyref mean on these three elements? It >uses the common definition in our spec, but that should really be >modified to something narrower (even if we state that it is undefined for >these three elements). > >Robert D Anderson >IBM Authoring Tools Development >Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]