W3C home > Mailing lists > Public > www-dom-ts@w3.org > May 2001


From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Date: Tue, 15 May 2001 14:51:13 +0200
Message-ID: <9F67DC27F4CCD311ABA600508B6A66A44A6418@VXOIMP1>
To: "'Arnold, Curt'" <Curt.Arnold@hyprotech.com>, Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Cc: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
Hi Curt

Thanks for your quick response

This is of course a proposal, so things are being put to discussion. I'll
try to answer your questions below:

-----Ursprungligt meddelande-----
Från: Arnold, Curt [mailto:Curt.Arnold@hyprotech.com]
Skickat: den 14 maj 2001 20:49
Till: 'Dimitris Dimitriadis'
Kopia: 'www-dom-ts@w3.org'
Ämne: RE: DOM TSML 0.9

I guess I have a couple of observations:

There seems to be no indication of how to set up the test, particularly what
document should be loaded.  Of course, all the NIST tests load "staff.xml"
that will be different when incorporating tests from difference sources.

*** This will presumably be in the test file when it is submitted to the
test suite. Of course it will vary from implementation to implemetation, but
could be up to the harness to resolve.

A generic <CALL> element is being used to call methods defined in the DOM
and provides information that could potentially conflict with the DOM spec.

  <parameters VALUE="0" TYPE="int" NUMBER="NONE" /> 

In this call, the generic <CALL> element specifies that the return type of
NodeList.item() is a Node and that the call takes one parameter.  Those are
already known from the DOM spec.  The test could be a lot cleaner, if the
to known DOM properties or methods were represented by something like:

<test id="elementAssociatedAttribute">
	<!-- maybe should assign public ID's to the well known test cases?
	<load href="staff.xml"/>
	<Document.getElementsByTagName tagName="address"/>
	<NodeList.item index="0"/>
	<NamedNodeMap.getNamedItem name="domestic"/>
	<!--  what I think this test was really trying to check
                  but the NIST harness didn't support  -->
	<assertEquals value="true"/>

*** Sure, but I'm not sure this goes for all tests. In this case you're
right, but I presume there are others where your simplified version wouldn't
be enough. We could keep the more advanced version, clean it up a bit, and
make more elements optional to keep the size down.

Since the tests can be identified by a URI, the metadata could be specified
using RDF:

<RDF:about href="http://www.w3.org/dom1test#elementAssociatedAttribute>
	<dc:Author>Mary Brady</dc:Author>

*** This is a very good point and I'd really like us to move along those
lines. Could you make some suggestions in document form? It doesn't add
functionality, but uses RDF, which in itself is a good thing (at least for
those of us who like it). 

The <TRY> element doesn't add information.  In this test, there is no
expectation of an exception so if any is encountered the test framework
identify it as a failure.  In cases where there is an expectation of an
exception, the exception is expected on one particular call and that
could be specified as part of the element for the call.

*** Perhaps it isn't well used in this particular test. Let me look at it
and get back to the list.

<CharacterData.substringData start="-1" end="10"

The date is not compatible with the XML Schema datatypes "date" type.

*** Again, thanks for your comments. I'll update the proposal. Do others
have any thoughts?

Received on Tuesday, 15 May 2001 08:51:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:02 UTC