- From: Michael Glavassevich <mrglavas@ca.ibm.com>
- Date: Mon, 12 Jan 2009 02:02:21 -0500
- To: public-webapps@w3.org
- Message-ID: <OFDA4B6644.7AD0FCB3-ON8525753C.0023922F-8525753C.00269E3B@ca.ibm.com>
Hi WG, The DOM Core specification and other DOM modules define feature strings [1] which applications can query to check whether or not a specific DOM module is supported by a DOMImplementation. For example, DOM Level 2 Traversal and Range [2] says: "A DOM application may use the hasFeature(feature, version) method of the DOMImplementation interface with parameter values "Traversal" and "2.0" (respectively) to determine whether or not this module is supported by the implementation." These feature strings are also useful for selecting a DOMImplementation which supports a specific set of features through the methods provided by DOMImplementationRegistry [3]. After reading the spec it doesn't seem like Element Traversal has such a string defined for it, so applications would have no standard way for selecting a DOMImplementation which supports Element Traversal or determining whether the DOMImplementation instance they already have supports it. Is there a reason a feature string was omitted from the spec? An oversight, perhaps? Can this be added to the errata? Thanks. [1] http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#DOMFeatures [2] http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113/traversal.html#Traversal-overview [3] http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#Bootstrap Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@ca.ibm.com E-mail: mrglavas@apache.org
Received on Monday, 12 January 2009 07:02:30 UTC