15688 2012-01-24 10:42:52 +0000 [XQ30] Effect of prohibiting the serialization option 2012-02-15 11:00:32 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Member-only Editors Drafts PC Windows NT RESOLVED FIXED P2 normal --- 1 tim jonathan.robie public-qt-comments oldest_to_newest 63046 0 tim 2012-01-24 10:42:52 +0000 It's pretty clear what effect prohibiting the following optional features will have: schema-import: Raise XQST0009 on schema import. schema-validation: Raise XQST0075 on validate expressions. static-typing: Don't raise XPTY0004, XPST0005 for some expressions. module: Raise XQST0016 on module declaration or module import. But it's not quite so clear what disabling the serialization feature will do. Does it cause an implementation-defined error to be raised if the user attempts to serialize the results of a query (via the implementation's API)? Does it cause errors to be raised when output declarations are encountered? Does it cause fn:serialize to raise an error? 64092 1 jonathan.robie 2012-02-14 15:15:25 +0000 (In reply to comment #0) > It's pretty clear what effect prohibiting the following optional features will > have: > > schema-import: Raise XQST0009 on schema import. > schema-validation: Raise XQST0075 on validate expressions. > static-typing: Don't raise XPTY0004, XPST0005 for some expressions. > module: Raise XQST0016 on module declaration or module import. > > But it's not quite so clear what disabling the serialization feature will do. If you disable the serialization feature, then: * You must not serialize the results of a query according to the serialization spec. * You still must support fn:serialize(), unless we make it an optional feature during CR - it is not an error to call fn:serialize() in a query if the serialization feature is disabled. * You can still do a vendor-defined serialization * You can still return results of a query in a non-serialized format, e.g. a DOM tree > Does it cause an implementation-defined error to be raised if the user attempts > to serialize the results of a query (via the implementation's API)? Our specification does not know anything about the implementation's API, this question is out of scope. > Does it cause errors to be raised when output declarations are encountered? No, this is not an error. > Does it cause fn:serialize to raise an error? No, this is not an error. 64093 2 jonathan.robie 2012-02-14 15:21:21 +0000 Jonathan will add a NOTE to clarify this in the spec. 64137 3 jonathan.robie 2012-02-15 11:00:32 +0000 We have decided that fn:serialize() must be provided by all implementations, but an implementation can simply raise an error when it is called if it chooses not to provide this functionality. I will mention this in the note in the previous comment. The actual specification will be in F&O.