[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XSLT, RDF, fragment identifiers

• To: xml-dev@l...
• Subject: RE: XSLT, RDF, fragment identifiers
• From: "Simon St.Laurent" <simonstl@s...>
• Date: Tue, 1 Jul 2003 13:40:35 -0400
• In-reply-to: <1E0CC447E59C974CA5C7160D2A2854EC097CD5@S...>

Peter.Hunsberger@s... (Hunsberger, Peter) writes:
>I'm not sure quite what the issue is?  Aren't URIs well enough defined
>that something like:
>
>   *[concat('#',substring-after(uri,'#')) = @rdf:resource]
>
>should behave predictably?  Or am I just missing something completely?

If I just want to match IDs, I can do something like that, and likely
will. (Probably combined with Uche's suggestions.)  

Fragment identifier interpretation can get far trickier than that,
though, especially given the possibilities in the XPointer Framework.  

http://www.w3.org/TR/xptr-framework/

For this case, I can probably stumble through, but there are plenty of
plausible (largely hypertextual) cases where XSLT/XPath's lack of
XPointer understanding will make life difficult.   XInclude's dodged
that bullet, in Section 4.2, but even that supports the element()
scheme.

(At the same time, I really don't want to pile anything additional into
those specs.  If I could swap out schema support in favor of XPointer
support - well, I'd think about that one and probably prefer it.)

-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org

• References:
  • RE: XSLT, RDF, fragment identifiers
    • From: "Hunsberger, Peter" <Peter.Hunsberger@s...>

• Prev by Date: Re: XSLT, RDF, fragment identifiers
• Next by Date: RE: XSLT, RDF, fragment identifiers
• Previous by thread: RE: XSLT, RDF, fragment identifiers
• Next by thread: RE: XSLT, RDF, fragment identifiers
• Index(es):
  • Date
  • Thread