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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

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


Subject: RE: [ebxml-cppa] PartyId proposal, modifications of ECOM proposal to consider.



Sorry, left out the hexadecimal value. So, '#' when cast to a number
corresponds to 35 in decimal notation and 0x23 in hexadecimal notation.
The '%' escapes are written with two hexadecimal digits, from 0x00 to
0xff.

Dale, 



So explanatory paragraph should've said:

However, if this change is still unclear, I think I can quote the
convention from the RFC 2141 in the text for convenience. [It is to use
the octet values represented in hexadecimal format with a "%" sign to
signal the start of escaping. So a "#" would, for example, be escaped by
using the string "%23" ]

==========

3. Punctuation marks in these formal names (such as, "/", "-" or "'" )
should be included unless they are not allowed in URNs  [RFC 2141]. If
the punctuation characters are not allowed in URNs, then the hexadecimal
escaping convention explained in [RFC 2141] should be followed for
characters not allowed in URNs. However, spaces are not allowed in URNs
and should be consumed during the production of an upper-camel-case
string, rather than preserved in an escaped form. Words in names that
are all upper-case should remain so when converted to an
upper-camel-case string.


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