Closed
Bug 176519
Opened 22 years ago
Closed 22 years ago
Implement IETF's xpath1() XPointer scheme
Categories
(Core :: XML, defect)
Core
XML
Tracking
()
RESOLVED
DUPLICATE
of bug 182323
mozilla1.3beta
People
(Reporter: itsnewsforme, Assigned: hjtoi-bugzilla)
References
()
Details
Since Mozilla already has a XPath 1.0 implementation, it should be quite trivial to add the XPointer scheme xpath1() as proposed by Simon St.Laurent. Another easy feature for Mozilla ...
Well, there is some dependency on XPointer, but not on the XPointer standard by W3C in the sense that in order to implement the xpath1() scheme, there is no need for all the schemes provided by the W3C XPointer standards. All we need is the basic framework, and in that sense I believe we can just use the current framework that is used with the FIXptr implementation. That is, even though we can use FIXptr[1] in today's builds (or at least we could the last time I checked), but we do not have an implementation of XPointer[2] working yet, the basic framework (that is, behaviour minus all the syntaxes for the different schemes) used by the two is the same. Adding support for IETF's xpath1() scheme has no dependency on all the schemes provided by [1] or [2], and since we have a working implementation of XSL (which uses XPath), we already have a working implementation of XPath 1.0, it should be minimal work with minimal possibility of bug creation. [1]http://lists.w3.org/Archives/Public/www-xml-linking-comments/2001AprJun/att-0074/01-NOTE-FIXptr-20010425.htm [2]http://www.w3.org/TR/xptr/
Updated•22 years ago
|
QA Contact: petersen → rakeshmishra
Assignee | ||
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → mozilla1.3beta
Assignee | ||
Comment 3•22 years ago
|
||
I actually have implemented this in other bug, marking this as dupe. *** This bug has been marked as a duplicate of 182323 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•