- From: Pat Hayes <phayes@ihmc.us>
- Date: Tue, 18 Oct 2005 12:05:04 -0500
- To: Bijan Parsia <bparsia@isr.umd.edu>
- Cc: public-ws-desc-comments@w3.org, "Henry S. Thompson" <ht@inf.ed.ac.uk>, public-ws-desc-comments-request@w3.org, Jonathan Marsh <jmarsh@microsoft.com>, Pat Hayes <phayes@ihmc.us>, David Orchard <dorchard@bea.com>
> >>BTW, one thing I still don't understand is why the parens cause a >>parsing problem. The XPointer syntax results in balanced parens so >>it should be easy to parse, e.g. when the URI-Reference is the >>argument of some function call. > >The problem is that Pat wants to use parentheses as token delimiters >*and* he wants URIs not *not* be specially quoted. So there's an >ambiguity from his perspective. You see this some times in mail >clients that "recognize" uris. E.g., > """Boris wrote it up (http://www.example.com), check it out."""" > >If the program is sticking to the spec the uri highlighted will be: > http://www.example.com), ), >Which is broken :) "Smart" clients will do: > http://www.example.com > >via an heuristic, which you clearly can't do for a formal grammar. > >So it's not the balancing, it's the using, especially as a >terminating character. For the record: yes, exactly. U/IRIs, I am coming to realize, cannot be treated as embedded text strings. They have to be placed in protective wrappers, or fully escaped, or somehow isolated from any surrounding text. No doubt this has been obvious to everyone for the longest time, and I am just waking up to reality. Sorry y'all got to hear my howling. Pat -- --------------------------------------------------------------------- IHMC (850)434 8903 or (650)494 3973 home 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 cell phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Tuesday, 18 October 2005 17:05:17 UTC