OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: Just the issues: encoding public ids as URNs


/ John Cowan <jcowan@reutershealth.com> was heard to say:
| Norman Walsh wrote:
| 
| > I've suggested that we use '+', ':', and ';', so we must have an
| > escaping mechanism for them when they occur literally. I propose
| > to add '$' to this list and require the following:
| > 
| >  $$ to represent a literal $
| >  $+ to represent a literal +
| >  $: to represent a literal :
| >  $; to represent a literal ;
| 
| For the record, all of these characters may be usefully %-escaped
| by both 2141 and 2396 rules.  That is, both 2141 and 2396 think
| that ":" and "%3A" are two different strings, unlike
| "_" and "%5F", which are 2141-distinct but 2396-identical.
| That's why I said they were "available".
| 
| Does that affect your position?

Oh. Um. Sorry I missed that. In that case, I guess I stand by what
I said earlier except that I'd simply %-encode literal '+', ':', and ';'
characters.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@East.Sun.COM    | The last act is bloody, however fine the
XML Standards Engineer       | rest of the play. They throw earth over
Technology Development Group | your head and it is finished for
Sun Microsystems, Inc.       | ever.--Pascal


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC