[Bug 20321] New: DOM <-> XDM Mapping

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 20321] New: DOM <-> XDM Mapping

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20321

            Bug ID: 20321
           Summary: DOM <-> XDM Mapping
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1 Requirements and Use Cases
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

It was considered in last Month's F2F meeting that we could add a mapping
between the XDM and the DOM (in the same way as there is one between the
Infoset and XDM, between PSVI and XDM).

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 20321] [XQ31ReqUC] DOM <-> XDM Mapping

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20321

Jonathan Robie <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|XQuery 3.1 Requirements and |Requirements for Future
                   |Use Cases                   |Versions
           Assignee|[hidden email]    |[hidden email]

--- Comment #1 from Jonathan Robie <[hidden email]> ---
In today's call we decided to move this to requirements for future versions.
It's not part of the minimum required to declare victory for 3.1.

The DOM=>Infoset mapping of the DOM and the Infoset=>XDM mapping of the XDM can
be used to define this, but there are some compatibility issues due to
differing versions of the DOM, interpretation of namespaces, etc., so this is
worth considering in a future version.

--
You are receiving this mail because:
You are the QA Contact for the bug.