OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] keyref= Attribute of href=

keyref's specification is on the roadmap for 1.2. In the meantime we probably need to say something like "reserved for future use", rather than the current wording.

Michael Priestley
IBM DITA Architect and Classification Schema PDT Lead

"W. Eliot Kimber" <ekimber@innodata-isogen.com>

01/02/2007 06:04 PM

[dita] keyref= Attribute of href="

The current draft of the language reference says:

"Currently not implemented in DITA
processors. Provides a key that a process
can use to look up associated

I have two problems with this:

1. The first sentence should not be in a specification since it may not
be true.

2. The second sentence is not sufficiently descriptive of the purpose of
the attribute. In particular, information associated with what? And for
what processing purpose. If this attribute is or is not present, what
processing result should I expect to see?

If this attribute is not implemented then it shouldn't be in the spec
(or should at least be deprecated) unless there's a well-documented use
case for it and that use is more clearly documented in the specification



W. Eliot Kimber
Professional Services
Innodata Isogen
9390 Research Blvd, #410
Austin, TX 78759
(214) 954-5198


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]