6 messages in org.oasis-open.lists.ditaRE: [dita] DITA v1.2 Review | @keys i...| From | Sent On | Attachments |
|---|---|---|
| Tarun Garg | Aug 31, 2010 9:55 pm | |
| Eliot Kimber | Aug 31, 2010 10:03 pm | |
| Tarun Garg | Sep 2, 2010 1:50 am | |
| Eliot Kimber | Sep 2, 2010 4:08 am | |
| Tarun Garg | Sep 3, 2010 11:36 pm | |
| Eliot Kimber | Sep 4, 2010 5:01 am |  .zip |
| Subject: | RE: [dita] DITA v1.2 Review | @keys in a conref | |
|---|---|---|
| From: | Tarun Garg (tar...@adobe.com) | |
| Date: | Sep 2, 2010 1:50:26 am | |
| List: | org.oasis-open.lists.dita | |
I thought we don't use conref, topicsetref, keyref & conkeyref resolution for
determining the keyspace. For keyref & conkeyref, it is very obvious that since
they depend on keyspace, these shall not be resolved until the keyspace is
determined completely. But for conref & topicsetref, it is possible that these
elements (prior to resolution), have key definitions on themselves or on any of
their descendants.
That brings the following questions to my mind:
1) For determining keyspace, should the conref & topicsetref be resolve?
2) If (1) is yes, should the key definitions be included from any of the
descentants of the conref/topicsetref target/referenced element (for conref
range this shall also means siblings from the target)
3) if (1) is no, should the key definitions be included from any of the
descentants of the conref/topicsetref referencing element
Regards, Tarun Garg | Adobe Systems | +91-120-2444711 | tar...@adobe.com
-----Original Message----- From: Eliot Kimber [mailto:ekim...@reallysi.com] Sent: Wednesday, September 01, 2010 10:34 AM To: Tarun Garg; dita Subject: Re: [dita] DITA v1.2 Review | @keys in a conref
In your example, the effective element after conref resolution is:
<topicref id="tr-02" keys="TR02" href="abc.dita"/>
By the rule that conreffing elements' attributes take precendence over the attributes of the conref target.
Assuming that map1.ditamap is otherwise included in the map tree, then both key TR01 and TR02 would be bound and both would be bound to resource "abc.dita".
Cheers,
Eliot
On 8/31/10 11:55 PM, "Tarun Garg" <tar...@adobe.com> wrote:
I am not able to identify the use of @keys at an element that is actually a conref. In case of a conref, the @href may be generally missing as that shall be derived from the referenced element.
Say for example, in a map there is topicref element which is actually a conref to a topicref element in another map.
In map1.ditamap: <map> SS. <topicref id=²tr-01² keys=²TR01² href=²abc.dita²/> SS. </map>
In map2.ditamap: <map> SS. <topicref id=²tr-02² keys=²TR02² conref=²map1.ditamap#tr-01²/> SS. </map>
What shall the key TR02 resolve to? As I understand, that resolves to nothing. Also, is there any specific use of such a key in a conref element, apart from defining a key that points to nothing. I am not ruling out the cases where such an element carries an @href as well. But in that case, the purpose of conref is undermined.
Regards, Tarun Garg | Adobe Systems | +91-120-2444711 | tar...@adobe.com
-- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php