[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Review #2 comment: Handling xrefs and conrefs within a conref
DITAweb URL: https://ditaweb.com/oasis-dita/#/00074601-DA$00073575-DB$Handling%20xrefs%20and%20conrefs%20within%20a%20conref Test in question: "When referenced content contains a content reference or cross reference, the effective target of the reference depends on the form of address that is used in the referenced content.
Comments: [Eliot Kimber] Options include: A. Resolve to the first instance of the ID following conref resolution and report the duplicate ID. This is the current behavior for duplicate IDs generally. B. Rewrite the IDs and references in the conreffed content so that the link resolves in the use context as it did in the source context. Option A is reasonable but option B makes content
more reusable when the re-used content is otherwise self
contained. I would like to propose making option B required but I
doubt the TC would be willing to impose that processing
requirement at this point. [Robert Anderson] OK, I've got that use case clear in my mind, using an actual
example here to clarify. Use case is something like this being
reused: In the new topic, id="first" already exists before the conref. So, in the new topic that pulls in the list above, does "#./first" resolve to the "first" that existed already in the topic, or to the list item that's pulled in with the conref? --
Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]