This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

XSL-FO: syntax for datatypes





I (rather late, sorry) noticed that in XSL-FO <integer> and <number>
literals (as specified on page 59 of the CR pdf file) allow an optional
+ before the digits. This is a rather surprising difference from XSLT
and XPath, considering how closely these specs are interrelated.
Probably the spec ought at least note the difference.

Also (page 61) id and idref are defined to take a Name, and references
the XML spec for Name, however the namespace spec (rather weakly)
specifies that IDs should be NCNames.


     An XML document conforms to this specification if all other tokens 
     in the document which are required, for XML conformance, to match
     the XML production for Name,
     match this specification's production for NCName.
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

         The effect of conformance is that in such a document: 

        All element types and attribute names contain either zero or one
        colon.  
        No entity names, PI targets, or notation names contain any colons. 

    Strictly speaking, attribute values declared to be of types ID,
    IDREF(S), ENTITY(IES), and NOTATION are also Names, and thus should
    be colon-free.
       ^^^^^^^^^^ 

I believe that MSXML (at least) enforces this.


David

(This message is being sent to xsl-list, copied to xsl-editors list)

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]