[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: [oasis-tcs/dita] What are the rules for nested conrefs within a conref push? (#346)
I asked the poster to resend this to dita-comment, but am
forwarding so that we can discuss at today's TC meeting.
Subject: | [oasis-tcs/dita] What are the rules for nested conrefs within a conref push? (#346) |
---|---|
Date: | Thu, 30 Jan 2020 13:13:58 -0800 |
From: | ChrisTrenkamp <notifications@github.com> |
Reply-To: | oasis-tcs/dita <reply+AAOG3BV3WSSJSSJ67TSH5E54IB4ZNEVBNHHCCPVQUQ@reply.github.com> |
To: | oasis-tcs/dita <dita@noreply.github.com> |
CC: | Subscribed <subscribed@noreply.github.com> |
I've searched the spec for an answer to this question to no avail: what happens when there's another conref within a conref push? The rules are clear with nested pulls, but it's not very clear with pushes.
<!-- source.dita -->
<p conaction="pushreplace" conref="other.dita#topic/ptag">
<codeblock conaction="pushreplace" conref="#./codetag">codeblock</codeblock>
</p>
<codeblock id="codetag">will this get replaced?</codeblock>
<!-- ... or what about... -->
<p conaction="pushreplace" conref="other.dita#topic/ptag">
<codeblock conref="#./codetag">codeblock</codeblock>
</p>
<codeblock id="codetag">will this be pulled?</codeblock>
What's supposed to happen with the codeblock
tag
in cases like these? Does the codeblock's source document
effectively become other.dita and gets resolved from there? Does
the codeblock's source document stay under source.dita
?
Is this forbidden?
â
You are receiving this because you are subscribed to this
thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]