dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [dita] Repeated conrefs
- From: Michael Priestley <mpriestl@ca.ibm.com>
- To: "Paul Prescod" <paul.prescod@blastradius.com>
- Date: Tue, 11 Oct 2005 06:36:04 -0400
Comments below...
Michael Priestley
IBM DITA Architect
SWG Classification Schema PDT Lead
mpriestl@ca.ibm.com
"Paul Prescod" <paul.prescod@blastradius.com>
wrote on 10/06/2005 07:50:36 AM:
> By definition, every element that is conrefed has an “id” attribute.
> Is it therefore invalid to conref the same element into the same
> topic twice?
It is still valid. The id on most elements is not
constrained to be unique, precisely to allow this as a valid case.
>And to conref the same topic into a parent topic
twice?
This is not so valid. Topic-level elements must have
unique ids. If the same topic gets conref'd into a document in multiple
places, this does produce an error once the resolved document is parsed,
and the conref processor doesn't currently check for that.
>
> Is it legal for an element with a DITA conref
to reference another
> element with a conref? If so, shouldn’t DITA disallow mutually
> recursive conrefs?
It should, it's just an edge case that is expensive
to check for, so I don't know of any process that currently does.
>
> And as an implementation question: how many validating
conref
> processors are known to exist and to support DITA semantics
> (including specialization, ID, filtering) explicitly?
The DITA Open Toolkit contains a specialization-aware
domain-checking conref transform. I believe filtering is done in a separate
step.
>
> Paul Prescod
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]