RE: [dita] Bug: fragref does not allow keyref

["Ogden, Jeff" <jogden@ptc.com>]

I don't care how we get there, but this isn't something that we should
be considering at this late stage of work on DITA 1.2.  The time for
such considerations came and went quite a long time ago.  Lets put it on
the DITA 1.3 list and move on.

    -Jeff

> -----Original Message-----
> From: Eliot Kimber [mailto:ekimber@reallysi.com]
> Sent: Monday, January 25, 2010 5:30 PM
> To: Robert D Anderson; Bruce Nevin (bnevin)
> Cc: dita
> Subject: Re: [dita] Bug: fragref does not allow keyref
> 
> On 1/25/10 4:19 PM, "Robert D Anderson" <robander@us.ibm.com> wrote:
> 
> > It also means allowing behaviors that were previously
> > forbidden.
> 
> But my point is that the current state *does not forbid*
> anything--href-based addressing is not and cannot be limited to any
> particular scope. Adding keyref doesn't make the scope of address any
> less
> unbounded.
> 
> My point is that *all* href-based addresses should have a
corresponding
> keyref, period. There's absolutely no justification for not doing so
> and
> therefore the lack of it is a bug.
> 
> Or said another way: addressing is distinct from link semantics and
> trying
> to impose any link semantics by limiting addressing is *fundamentally
> wrong*. Which means that in this regard *DITA has always been broken*.
> 
> I realize it's not necessarily a critical bug. I only noticed it
> because I
> added fragref and synnoteref to the list of linking elements and only
> then
> realized the last of keyref.
> 
> Note that I'm not arguing against the restriction on scope of
reference
> (necessarily), just arguing that the presence of href *demands* keyref
> and
> that that demand is completely distinct from any semantic of any link
> for
> href is meaningful.
> 
> 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:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php