OASIS Darwin Information Typing Architecture (DITA) TC

 View Only

  • 1.  keyref= Attribute of href=

    Posted 01-02-2007 23:05 
    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
information."

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 
itself.

Cheers,

Eliot

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

ekimber@innodata-isogen.com
www.innodata-isogen.com


  • 2.  Re: [dita] keyref= Attribute of href=

    Posted 01-02-2007 23:18 

    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
    
mpriestl@ca.ibm.com
    
http://dita.xml.org/blog/25


    

    

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

    01/02/2007 06:04 PM

    		

    

    


    To
    
    		<dita@lists.oasis-open.org>

    


    cc
    
    		

    


    Subject
    
    		[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
    
information."

    
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
    
itself.

    
Cheers,

    
Eliot

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

    
ekimber@innodata-isogen.com
    
www.innodata-isogen.com


Related Content