- From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Date: Fri, 2 Dec 2011 13:25:12 +0000
- To: Steven Pemberton <Steven.Pemberton@cwi.nl>
- CC: Forms WG <public-forms@w3.org>
- Message-ID: <E9F5BB68-592A-4CE7-AEBD-D25FDE57D1E7@inventivegroup.com>
Some extra info so that we can discuss it faster on the phone: * name: not applicable, it is used for referencing later * byte-order-mark: The byte order mark may be undesirable under certain circumstances; for example, to concatenate resulting XML fragments without additional processing to remove the byte order mark. Therefore this specification does not mandate the byte-order-mark parameter to have the value yes when the encoding is UTF-16, even though the XML 1.0 and XML 1.1 specifications state that entities encoded in UTF-16 must begin with a byte order mark. Consequently, this specification does not guarantee that the resulting XML fragment, without a byte order mark, will not cause an error when processed by a conforming XML processor. * escape-uri : Not applicable for XML serialization * include-content-type: Not applicable for XML serialization * normalization-form: Has to do with how to serialize unicode text -> could be handy if you need it… * undeclare-prefixes: Maps the prefix to the empty namespace if the prefix is defined on the node in the Data Model (not sure how this can occur in XForms) * use-character-maps : Used to do character replacements Kind regards, Nick Van den Bleeken R&D Manager Phone: +32 3 821 01 70 Office fax: +32 3 821 01 71 nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com> www.inventivedesigners.com [cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110] On 02 Dec 2011, at 11:27, Steven Pemberton wrote: In the submission element (http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_submission_Element_2) we use a number of attributes for XML serialization that we took from the output element of XSLT 1.0 (we use all except doctype-public and doctype-system). This is just a heads up that XSLT 2.0 added some more, that we may want to decide on one way or the other. XSLT 1.0: http://www.w3.org/TR/1999/REC-xslt-19991116#output <xsl:output - method = "xml" | "html" | "text" | qname-but-not-ncname version = nmtoken encoding = string omit-xml-declaration = "yes" | "no" standalone = "yes" | "no" - doctype-public = string - doctype-system = string cdata-section-elements = qnames indent = "yes" | "no" media-type = string /> XSLT 2.0: http://www.w3.org/TR/xslt20/#element-output <xsl:output + name? = qname - method? = "xml" | "html" | "xhtml" | "text" | qname-but-not-ncname + byte-order-mark? = "yes" | "no" cdata-section-elements? = qnames - doctype-public? = string - doctype-system? = string encoding? = string + escape-uri-attributes? = "yes" | "no" + include-content-type? = "yes" | "no" indent? = "yes" | "no" media-type? = string + normalization-form? = "NFC" | "NFD" | "NFKC" | "NFKD" | "fully-normalized" | "none" | nmtoken omit-xml-declaration? = "yes" | "no" standalone? = "yes" | "no" | "omit" + undeclare-prefixes? = "yes" | "no" + use-character-maps? = qnames version? = nmtoken /> Steven -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ________________________________ Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
Received on Friday, 2 December 2011 13:25:49 UTC