- From: Alex Milowski <alex@milowski.org>
- Date: Mon, 14 May 2007 19:35:32 -0700
- To: "XProc WG" <public-xml-processing-model-wg@w3.org>
- Message-ID: <28d56ece0705141935g2c197cf2seb414783289e9166@mail.gmail.com>
I've gone back through the archives to pull out issues that we've had with the step library. For some of them, the e-mail threads seemed to end in a decision that I've tried to detail below. Please let me know if I've missed any issues. In no particular order: 1. boolean option values - 'yes|no' versus 'true|false' ? We have steps that have options that use 'true' and 'false' values and we have one ('status-only' on http-request) that uses 'yes' and 'no' values. We also use 'yes' and 'no' in our specification. Doesn't it make sense to have these all in sync? Also, shouldn't we be use an XML Schema simple type (e.g. xs:boolean) ? 2. Add a 'content-type' option to the p:unescape-markup step. This option would accept a media type. If the media type is recognized by the processor, parsing according to the media can be performed and that behavior is implementation defined with the exception of any XML media type (i.e. text/xml, application/xml, and *+xml types). There is no default value and the step assumes XML parsing without a value. http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0105.html 3. Wrapping a sequence: Do we want a separate step type? Should the 'name' option name be changed? http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0143.html 4. Http-request review - header conflicts http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0138.html - invalid method creates a dynamic error - href uri isn't a HTTP-based protocol (allows for https) http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0101.html - multiple bodies is now handled by multipart: http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0100.html - making it required http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0000.html 5. Should we rename p:xslt to p:xslt1 6. p:load options 'validate' and 'namespace-support' The 'validate' option would control DTD validation. The 'namespace-support' would turn on or off namespace processing. http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0091.html 7. p:escape-markup issues? - Given a match pattern via an option called 'match', it will escape particular elements (e.g. the RSS description element). http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0008.html 8. p:aggregate again http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Apr/0229.html 9. General validation http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Apr/0225.html 10. split-sequence http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Apr/0171.html 11. count/tee proposals - Should tee be removed now that we have journaling ? - Should count remain? 12. p:save/p:serialize proposal This is part of the forthcoming proposal on serialization. http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007Apr/0139.html 13. p:label issue? http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2007May/0087.html -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Tuesday, 15 May 2007 02:35:37 UTC