13 messages in org.oasis-open.lists.ditaRE: [dita] Bug: fragref does not allo...| From | Sent On | Attachments |
|---|---|---|
| Eliot Kimber | Jan 24, 2010 11:41 am | |
| Eliot Kimber | Jan 24, 2010 11:47 am | |
| Robert D Anderson | Jan 25, 2010 6:15 am | |
| Ogden, Jeff | Jan 25, 2010 6:21 am | |
| Eliot Kimber | Jan 25, 2010 6:22 am | |
| Bruce Nevin (bnevin) | Jan 25, 2010 9:15 am | |
| Robert D Anderson | Jan 25, 2010 9:52 am | |
| Bruce Nevin (bnevin) | Jan 25, 2010 12:45 pm | |
| Robert D Anderson | Jan 25, 2010 2:19 pm | |
| Eliot Kimber | Jan 25, 2010 2:29 pm | |
| Ogden, Jeff | Jan 25, 2010 2:48 pm | |
| Bruce Nevin (bnevin) | Jan 26, 2010 6:52 am | |
| Eliot Kimber | Aug 30, 2011 9:11 am |
| Subject: | RE: [dita] Bug: fragref does not allow keyref | |
|---|---|---|
| From: | Ogden, Jeff (jog...@ptc.com) | |
| Date: | Jan 25, 2010 6:21:40 am | |
| List: | org.oasis-open.lists.dita | |
Don't these notes from the @href descriptions for fragref and synnoteref make @keyref irrevalant on these elements?
The referenced fragment should be in the same diagram as the fragref element.
Points to the target syntax note (<synnote>), which must be in the same syntax diagram.
-----Original Message-----
From: Eliot Kimber [mailto:ekim...@reallysi.com]
Sent: Sunday, January 24, 2010 2:48 PM
To: Eliot Kimber; dita
Subject: Re: [dita] Bug: fragref does not allow keyref
On 1/24/10 1:41 PM, "Eliot Kimber" <ekim...@reallysi.com> wrote:
The fragref element is a specialization of topic/xref. As currently
declared
it does not allow @keyref, only @href. I can't think of any reason
it
shouldn't also allow @keyref. This looks like a bug to me.
Ditto synnoteref, which explicitly allows referencing notes from other
syntax diagrams, which makes allowing @keyref essential.
Cheers,
E.
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
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: