OASIS DocBook TC2

 View Only

Re: [docbook-tc] First crude attempt at DocBook V5 spec

  • 1.  Re: [docbook-tc] First crude attempt at DocBook V5 spec

    Posted 02-16-2005 14:31
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    docbook-tc message

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


    Subject: Re: [docbook-tc] First crude attempt at DocBook V5 spec


    Norman Walsh wrote:
    
    > It's pretty crude, but it's also done 24 hours before the meeting.
    > Almost :-)
    
    Yep, it is hard to cheat time if you have NTP client installed :-)
    
    Thanks, Norm. Please find my mostly editorial notes inline:
    
    > Copyright © 2001, 2002, 2003, 2004 The Organization for the Advancement of 
    
    We should add 2005 here.
    
    > *Table 1. DocBook Element Changes*
    > 
    > |action|, |beginpage|, |highlights|, |interface|, |invpartnumber|, |medialabel|, 
    > |modespec|, |structfield|, |structname| 	
    > 
    > Deleted.
    
    Do we really want to remove structfield and structname from DocBook? I 
    think that not all programs are written in OO languages in these days 
    and that there are a lot of people writing in pure C that will benefit 
    from these elements.
    
    Probably we should ask at docbook list if there is anyone using these 
    elements before we will definitively remove them.
    
    >         3.1.9. Universal Linking
    > 
    > Starting with DocBook V5.0, the |linkend| and |href| attributes are available on 
    > almost all elements.
    > 
    > The |linkend| attribute provides an ID/IDREF link within the document. The 
    > |href| attribute provides a URI-based link.
    > 
    > The |olink| and |ulink| elements have been removed from DocBook as these linking 
    > constructs can now be achieved directly from the appropriate inline (such as 
    > |productname| or |command|). For instances where no specific semantic inline is 
    > needed, |link| is still available.
    
    I think that we should mention here that href attribute is taken from 
    XLink namespace and thus there is no further need for distinguishing 
    between link/ulink/olink on markup level.
    
    >     C. Notices
    > 
    > Copyright © The Organization for the Advancement of Structured Information 
    > Standards [OASIS] 2001, 2002, 2003, 2004. All Rights Reserved.
    
    
    Add 2005 here.
    
    >  Normative Reference
    
    I think that we should add XLink Rec here:
    
    	http://www.w3.org/TR/xlink/
    
    Probably we should also include reference to your recent XLink note to 
    address xlink:type="simple" annoyances.
    
    >       Non-Normative References
    
    What about adding RNC tutorial:
    
    	http://relaxng.org/compact-tutorial-20030326.html
    
    
    See you (hear you;-) later,
    
    				Jirka
    
    -- 
    ------------------------------------------------------------------
       Jirka Kosek     e-mail: jirka@kosek.cz     http://www.kosek.cz
    ------------------------------------------------------------------
       Profesionální školení a poradenství v oblasti technologií XML.
          Podívejte se na náš nově spuštěný web http://DocBook.cz
            Podrobný přehled školení http://xmlguru.cz/skoleni/
    ------------------------------------------------------------------
    
    

    S/MIME Cryptographic Signature



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