RE: [dita] DITA 1.3 Proposal 13004: Scoped Keys

I'd actually intended that conref resolution occur, but not conkeyref resolution, but if it's better to skip conref resolution for the sake of kespace construction entirely, I'm fine with that.

Chris

-----Original Message-----
From:  [mailto:] On Behalf Of Eliot Kimber
Sent: Monday, January 23, 2012 3:37 PM
To: Eliot Kimber; dita
Subject: Re: [dita] DITA 1.3 Proposal 13004: Scoped Keys

On 1/23/12 12:38 PM, "Eliot Kimber" <> wrote:

> Based on my initial reading I'm happy with the proposal as written as far as
> it goes. However, there are a number of cases it doesn't address that I
> think need to be worked out.

7. Clarify that all key scope construction must occur *before* conref
processing is performed, as is the case with key space construction in DITA
1.2.

The proposal says the content of a key scope includes:

"The key scope-defining element¹s contents after conref resolution."

That's fine as long as we explicitly exclude any key definitions that are
present only because of conref. That is, if the result of conref resolution
results in new key definitions coming into the key scope, those definitions
are ignored because the scope's key space will already have been
constructed.  

Because conrefs may involve keys, it is not possible to do conref resolution
before key space construction is complete. The alternative would be to
perform all non-keyref-based conrefs, then do key space construction, then
resolve the remaining conrefs, but that seems pretty twisted.

Cheers,

E.


-- 
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com


---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: