DRs related to Part names

Chris Rae Chris.Rae at microsoft.com
Mon May 20 23:20:30 CEST 2013

Hi all - many thanks for reposting this, Murata-san. As we mentioned on the WG4 call last week, John and I have been looking through this document and have a couple of questions:

1. From item 2: As we discussed on the conference call, we think that ISO/IEC 295000 does not intent permitting a part name with a trailing slash, but the non-terminal ipath-absolute in RFC 3987 does. To this end, we think that we should define part name as 1*("/" isegment-nz).

2. From item 2: The list of constraints is a subset of the original constraints in 9.1.1. Can you remember why the other constraints weren't included?

3. From item 2: Are asterisk and colon characters to be prohibited entirely inside part names, or are we prohibiting only part names that are an asterisk or colon in their entirety?

4. From item 12: Please can you specify which exact five steps are removed from the conversion procedure?


-----Original Message-----
From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: 09 April 2013 06:43
To: SC34
Subject: OPC: DRs related to Part names

Dear colleagues,

Quite a few DRs are about part names.  These DRs are:

09-0280, OPC: Non-ASCII characters in Part Names 09-0283, OPC: Inconsistencies between Clause 9.1 and Annex A 09-0284, OPC: part-URI and part-IRI grammar productions 09-0285, OPC: Use of Terms "Part URI" and "Part IRI"
09-0286, OPC: The syntax of "references"
09-0288, OPC: Target attribute value needed to reference OPC parts 09-0291, OPC: Use of term "Unicode string"
09-0292, OPC: Space characters in part names

A WG4 document from Japan, namely
WG4 N0207, proposes solutions to all of them.


Before we start drafting this solution., I would like to make sure that everybody is happy with the proposed solution.
Comments welcome.


More information about the sc34wg4 mailing list