[Bug 14752] New: The "method" output parameter is NOT enough when it comes to extending the serialization-parameters schema


           Summary: The "method" output parameter is NOT enough when it
                    comes to extending the serialization-parameters schema
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Serialization 3.0
        AssignedTo: zongaro@ca.ibm.com
        ReportedBy: gabipetrovay@gmail.com
         QAContact: public-qt-comments@w3.org

As one can see, the "method" output parameter in the serialization-parameters
schema allows extension for implementations to define their own output method.
The most obvious example is the "binary".

But there are plenty other examples where only one output method is not enough.
People need to define options for the output method.

See for example:

Extra options are necessary for some output methods. So allowing any
implementation defined output method is like giving a kid a transparent candy
box that he cannot open.

Moreovert implementers (i.e. BaseX, eXist) have, for example, JSON converters
but all work different.

Having in the schema the flexibility to add extra serialization parameters
would allow people to start talking (EXPath) about common features in terms of
serialization. Envision for example:
EXpath could go one step further and define those methods and their parameter.

This way most serialization can go through fn:serialize and will simplify many
modules and spare developer brain cycles.


Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 10 November 2011 09:39:58 UTC