W3C home > Mailing lists > Public > public-html@w3.org > June 2008

[Fwd: [Bug 5744] Improved Fragment Identifiers]

From: Erik Wilde <dret@berkeley.edu>
Date: Fri, 13 Jun 2008 15:58:34 -0700
Message-ID: <4852FB9A.6020903@berkeley.edu>
To: public-html@w3.org

-------- Original Message --------
Subject: [Bug 5744] Improved Fragment Identifiers
Date: Fri, 13 Jun 2008 22:54:40 +0000
From: bugzilla@farnsworth.w3.org
References: <bug-5744-1720@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5744


Erik Wilde <dret@berkeley.edu> changed:

            What    |Removed                     |Added
----------------------------------------------------------------------------
          Resolution|WONTFIX                     |NEEDSINFO




--- Comment #4 from Erik Wilde <dret@berkeley.edu>  2008-06-13 22:54:39 ---
(In reply to comment #3)
> > http://www.codedread.com/fxpointer/ is an attempt to do something about it
> Yeah, that's the kind of thing I mean. Does it have many users?

we'll see. the author is on the public-html list and will probably reply
soon...

> I guess I'm not convinced that there is a real need here, and that even if
> there is a need, that it's not already solved by XPointer. We shouldn't be
> reinventing the wheel just because we're not sure we like the current spec --
> we should work with that spec to make it better.

xpointer is a half-finished set of specs that was basically abandoned 
when the
xml linking working group disappeared. people seem to think xpointer is
something finished and readily available that could simply be reused - i 
don't
think this is the case.

> So in conclusion I recommend approaching the XPointer group and asking them to
> make the improvements you feel it needs, possibly simplifying it if necessary,
> or explicitly saying it should work with HTML if that isn't already the case.

there is no xpointer working group. the xml linking working group 
disappeared a
number of years ago.

> If you disagree with this conclusion, please either show what information I
> overlooked in reaching my conclusion, or, if you agree with the facts but
> disagree with the interpretation of the facts, raise this issue with one of our
> chairs. Thanks!

so one conclusion of yours was that you don't think something like that is
necessary. it is hard to argue against that. the other conclusion was that
maybe xpointer should be adopted. here i would say that (a) xpointer is a
half-ready set of specifications, and (b) it is not being developed 
anymore, so
if we want better fragment identification beyond @ids, we have to do it
ourselves.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.

-- 
erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
        dret@berkeley.edu  -  http://dret.net/netdret
        UC Berkeley - School of Information (ISchool)
Received on Friday, 13 June 2008 22:59:15 GMT

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