OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   XPointer WD comments

[ Lists Home | Date Index | Thread Index ]
  • From: Lars Marius Garshol <larsga@ifi.uio.no>
  • To: xml-dev@ic.ac.uk
  • Date: Tue, 25 Aug 1998 15:50:04 +0200 (MET DST)

I've just returned to my XPointer implementation and updated it,
adding support for more of the specification. Because of this I have
some new questions and reflections on the draft:

 - The definition of the term 'resource' in section 1.3 seems to me
   both circular with 'locator' and also rather unclear.

 - The WD says nothing whatever about what kinds of errors exist and
   what to do with them. To me it seems sensible to operate with three
   kinds of errors: 

     - syntactic ones, where the locator fails to conform to the
     - semantic ones, where the locator does not make sense, such as
     - simple failures, where the locator attempts to locate
       non-existent nodes, such as child(4) on an element with three
       child elements

 - The WD does not say anything about how to interpret locator terms 
   using nodes located with the 'string', 'attr' or 'span' keywords as
   the source of a locator. Ie: what is the child(1) of a span?

 - Similarly, nothing is said about how to continue locating from a
   list of candidate nodes, such as in root().child(all).child(1)

 - According to the WD, a 'string' location term can locate a string
   that stretches across several different nodes. This seems to me
   both difficult to implement and somewhat unecessary, since as far
   as I can see the same could be achieved by use of the 'span' term.

 - Maybe a non-normative appendix to the spec should add something
   about how to represent 'span' results in terms of the DOM? Should
   one use a nodelist or a new node class?

 - Does the A.2 section indicate that a future version of the XPointer
   spec will include a formal description of XPointer semantics in
   terms of the DOM?

 - Nothing whatever is said about the data model on which XPointers
   operate, which means that issues like entity handling and attribute
   defaulting are not covered. For instance, would the XPointer 
   string("lars") match anywhere in the following instance?

   <!DOCTYPE ex [
     <!ENTITY a "a">


--Lars M.

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS