W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re[2]: #:body.h2[5]

From: Dmitry Turin <html60@narod.ru>
Date: Thu, 28 Jun 2007 11:23:13 +0300
Message-ID: <1449530721.20070628112313@narod.ru>
To: public-html@w3.org

Good day, Dro.

DT> <a src="a/b/c/d.htm#:body.h1[3]+h2[2]+h3[5]+p[8]">
DG> http://www.w3.org/TR/xptr/

(1.1) Xptr does not have abbreviated syntax for 'following-sibling',
especially for so combination with it, as
 following-sibling::*/descendant-or-self::TAG[position()=1]
Thus mark plus is necessary for usability.

(1.2) Mark plus has the different meaning, than
 following-sibling::*/descendant-or-self::TAG[position()=1]
because last expression finds several TAG,
but mark plus finds only _first_ TAG.
Thus mark plus is necessary for functionality.

(2) Expressions with function 'contains' is less usable (is more bulky),
than expression with braces
<a href="./a.htm#:h3{part of header}">
<a href="./a.htm#:img{k/m/n/pic.jpg}">
Imagine 'contains' in path !

(3) There is no visual comfort,
if path-es before and after #: use identical separator slash.
It's necessary to prefer different separators,
e.g. slash before and dot after for usability, i.e.
it's necessary to prefer
<a href="a/b/c/d.htm#:html.body.p.em">
over
<a href="a/b/c/d.htm#:html/body/p/em">
  

Dmitry Turin
HTML6     (6.1.0)  http://html60.chat.ru
SQL4      (4.1.0)  http://sql40.chat.ru
Computer2 (2.0.2)  http://computer20.chat.ru
Received on Thursday, 5 July 2007 06:52:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT