The normative/non-normative
strategy I heard articulated at some point was to state the desired outcome and
leave it to the implementor to figure out how to get there.
If we followed that strategy,
then the way the OT handles @href could be given as an example. This seems to me
a way of having our non-normative cake and eating it too in the form of examples
of the implementation strategy that the OT uses.
Re treatment of further
references from within the referenced content:
What is the desired
outcome?
How does the OT deal with that
now, and could that be cited as an example for reaching the desired
outcome?
/Bruce
From: Ogden, Jeff [mailto:]
Sent: Monday, November 09, 2009 9:57 AM
To:
dita
Subject: RE: [dita] Conref of topicref to topicref: are
relative URIs rewritten?
Does the DITA OT adjust all of the href values within
conrefed content or just the href values on the referenced
element?
Does the DITA OT adjust referencing attribute values
beyond @href? An example would be @conref and there are others.
Where does the following case fall in this
discussion?
File: t1.dita
<topic id="t1">
...
<p id="p1">Para1 in
t1</p>
<p id="p2">
<xref href="#t1/p1"
/>
...</p>
</topic>
File: t2.dita
<topic id="t2">
...
<p id="p1">Para1 in
t2</p>
<p
conref="t1.dita#t1/p2" />
...
</topic>
When topic t2 is processed:
1.
is the xref in error because the id "t1" doesn't exist
in topic t2?
2.
or is the xref a link to p1 in t1?
3.
or should the href value be rewritten to give a link
to p1 in t2?
All I'm saying is that there are a number of cases to
consider once you start down the road of adjusting things and I worry about
approaching this piecemeal for DITA 1.2 in a rush at the last minute without a
formal proposal and with only a short time for discussion (unless we slip the
DITA 1.2 deadlines further and perhaps that is what we should do given all of
the questions that have been raised recently).
-Jeff
>
