- From: Benjamin C. Chang <Ben.Chang@oracle.com>
- Date: Wed, 25 Jun 2003 23:23:55 -0700
- To: Curt Arnold <carnold@houston.rr.com>
- CC: Philippe Le Hegaret <plh@w3.org>, WWW DOM <www-dom@w3.org>
We have decided to keep isElementDefined[NS], as implementations
could be more efficient if left as currently defined and there are no
compelling reasons to eliminate or move these methods. The suggestion
about adding contains[NS] to DOM L3 Core will be considered.
Thanks,
Ben
Curt Arnold wrote:
> Philippe Le Hegaret wrote:
>
> >On Mon, 2003-06-02 at 23:45, Curt Arnold wrote:
> >
> >
> >>The current public working draft of L3 Core does not define NameList. I
> >>assume that it is defined in the current working group draft. If
> >>NameList has a provision to creation of nodes from a name entry, then I
> >>would be satisified with the resolution.
> >>
> >>
> >
> >Here is the current NameList interface as defined in the incoming
> >version of the Core draft (to be published really soon):
> >
> >// Introduced in DOM Level 3:
> >interface NameList {
> > DOMString getName(in unsigned long index)
> > raises(DOMException);
> > DOMString getNamespaceURI(in unsigned long index)
> > raises(DOMException);
> > readonly attribute unsigned long length;
> >};
> >
> >It does not define a method to create an Element or Attr node, but doing
> >so can be achieved easily using the createX() methods.
> >
> >
> >
> >>I do believe it would be essential to have a coordinated release of a
> >>Core public draft with the next public working draft of L3 validation.
> >>
> >>
> >
> >Our current effort is focused on updating the Core and Load/Save drafts
> >so those drafts should be back in sync soon.
> >
> >Philippe
> >
> >
> >
> >
>
> Adding
>
> boolean contains(DOMString name);
> boolean containsNS(DOMString namespace, DOMString localName);
>
> might allow the elimination of ElementEditVal.isElementDefined[NS]
Received on Thursday, 26 June 2003 02:24:09 UTC