W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2004

Implementation report update: pxdom

From: Andrew Clover <and-w3@doxdesk.com>
Date: Thu, 19 Feb 2004 13:11:45 +0000
To: www-dom@w3.org
Message-ID: <20040219131145.GC30090@doxdesk.com>

Just a quick update regarding the status of pxdom. Since the previous
Implementations report, pxdom 1.0 has been released, adding support
for the last couple of optional domConfig parameters and making the
relevant changes from the PR.

So, 1.0 supports the complete specification with the exception of:

 - external resource resolution & loading [forthcoming in 1.1]
 - any kind of validation  [not likely to be implemented soon]
 - asynchronous LSParsers  [not likely to be implemented soon]

It passes the DOM-TS level3/core and level3/ls test suites from
today's CVS snapshot with the exception of the following tests
which fail:

    (does not raise an error for Level 1 nodes; depends on issue
    raised in previous www-dom post)
  documentnormalizedocument06, documentnormalizedocument07,
  domconfigelementcontentwhitespace1, domconfigerrorhandler1,
  domconfigschemalocation1, nodegettextcontent19,
  nodeisequalnode03, textreplacewholetext08, LSSerializerConfig8,
  LSSerializerConfig10, DOMEntityResolverTest0
    (for varied reasons believed to be suite issues, see tracker)

and the following tests, which are skipped;

  attrgetschematypeinfo01-05, datatypenormalization01-06,
  elementgetschematypeinfo01-02, nodegetbaseuri19-20,
  attrisid04-05, typeinfoisderivedfrom01-62,
  entitygetinputencoding03-04, entitygetxmlversion03-04,
  entitygetxmlencoding03-04, DOMEntityResolverTest1
    (due to requirement of validating or schemaValidating
    (due to requirement of LS-Async feature)
    (DOMImplementationRegistry is not yet bound in Python)

Andrew Clover
Received on Thursday, 19 February 2004 08:33:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:12 UTC