RE: DR 09-0292 - OPC: Space characters in part names

[Francis Cave]

What is the problem with having a percent-encoded space character in a Part
name? There is no problem converting a Unicode space to the percent-encoded
form for an IRI, just as all other Unicode characters that don't belong to
the set of reserved and unreserved IRI characters have to be
percent-encoded. I see no obvious reason to exclude it. An example would, as
Murata-san suggests in the DR, be useful.

Incidentally, in A.1 "a Unicode string is converted to an IRI by
percent-encoding each ASCII character that does not belong to the set of
reserved or unreserved characters as defined in RFC 3986" doesn't make
sense, because "ASCII character" should read "Unicode character". Has a
defect report already been submitted on this point?

Francis



> -----Original Message-----
> From: Chris Rae [mailto:Chris.Rae at microsoft.com]
> Sent: 12 August 2010 19:32
> To: e-SC34-WG4 at ecma-international.org
> Subject: DR 09-0292 - OPC: Space characters in part names
> 
> http://cid-
> c8ba0861dc5e4adc.office.live.com/view.aspx/Public%20Documents/2009/DR-
> 09-0292.docx
> 
> This DR asks whether the space character is permitted in OPC part
> names. In 9.1.1.1 the standard states, "A Part name shall be an IRI and
> shall be encoded as either a Part IRI or a Part URI."  The ABNF for
> part-IRI and part-URI do not include space as a valid character. So the
> actual part name cannot contain a space. As far as converting Unicode
> strings goes, A.1 states, "a Unicode string is converted to an IRI by
> percent-encoding each ASCII character that does not belong to the set
> of reserved or unreserved characters as defined in RFC 3986."  The
> space characters is not part of the definitions of reserved or
> unreserved in the RFC.
> 
> I think it's reasonably clear that spaces are not permitted in part
> names, but I'd agree that it's something implementers might want to
> have made more obvious. I propose that we resolve this DR by adding an
> example to the existing table in A.4 (informative), incorporating a
> Unicode string with a space in it.
> 
> Any objections?
> 
> Chris