Proposed overview/scope of work for OPC revision

Thu Jan 9 20:54:39 CET 2014

It's linked on https://www.assembla.com/spaces/IS29500/wiki/OPC_Revision under Reference Material > WG 4 Documents / Mailing List: WG 4 N 0207 from Sept 2011 (http://kikaku.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2011-0207.html).  Related, his comments document on Annex A.3 is also listed under the same heading.

From: Chris Rae [mailto:Chris.Rae at microsoft.com]
Sent: Thursday, January 9, 2014 9:19 AM
To: SC34
Subject: RE: Proposed overview/scope of work for OPC revision

I think another good addition to this would be the content of Murata-san's summary document (N207, from 2011-09-08). I have a copy of this but I think the online one went missing with the loss of the document library. Murata-san - do you have a more recent version of this than the 2011-09-08 one? If not then I'd be happy to integrate that version into the Wiki.

Chris

From: John Haug [mailto:johnhaug at exchange.microsoft.com]
Sent: 08 January 2014 16:21
To: SC34
Subject: RE: Proposed overview/scope of work for OPC revision

I found additional useful information in e-mail.  Given that, the below and the "Relevant documents" e-mail from Murata-san, I created on the WG 4 Assembla site:

1.       An OPC revision front page listing the proposed scope of work and reference material - https://www.assembla.com/spaces/IS29500/wiki/OPC_Revision

2.       A work details page pulling together summary info relevant to the various categories of work - https://www.assembla.com/spaces/IS29500/wiki/OPC_Details

#2 includes a set of conclusions Murata-san and I drew and documented back in June.  I just noticed while looking back at that e-mail that it was never sent to the WG 4 mailing list.  All of that info is now on the Wiki for your perusal.  It nicely summarizes what exactly a relative reference is and how they are resolved.

#2 also includes a quick reference noting the small differences in the characters allowed in URIs, IRIs and LEIRIs.  One page with ABNF.

I hope all of this will be useful for establishing a clear idea of our intended work and for getting back up to speed on the details.  Please update it as appropriate with any additional useful info you find.

John

From: John Haug [mailto:johnhaug at exchange.microsoft.com]
Sent: Tuesday, January 7, 2014 4:17 PM
To: SC34
Subject: Proposed overview/scope of work for OPC revision

To reach consensus on scope and to better understand what we're intending to accomplish before we get lost in details, may I suggest the following as the list of topics we want to address in our changes to Part 2?  All open DRs marked for Part 2 should be included below.  Anything to add/remove/change before we agree on what we're going to do?

I'm going to try to organize a set of reference info, more thorough than the short list I sent out quickly on Thursday, to include numerous of old e-mail threads, documents, etc.  If I am able to do so, I may put it on a new Wiki page on the WG 4 Assembla wiki (https://www.assembla.com/spaces/IS29500/wiki).  I would also add the below, plus changes.

1. Combining IRI/URI

*         09-0280 - general DR about sections of OPC assuming non-ASCII is disallowed

*         09-0281 - terminology; all uses of "part" should specify what kind of part is meant

*         09-0283 - similar to 09-0280

*         09-0284 - terminology; need to re-associate the ABNF term names with the prose for part names

*         09-0285 - terminology; use of "part IRI" and "part URI"

*         09-0286 - need to update 9.2 (Part Addressing) to specify the format of a reference, based on the changes to be made to 9.1.1 (Part Names)

*         09-0288 - same as 09-0286, but for 9.3.2 (Relationship Markup)

*         09-0291 - terminology; specify what "Unicode string" means, based on the changes to be made to 9.1.1

*         09-0292 - which characters are allowed in a part name (e.g., whitespace, delimiters, special characters)

*         13-0002 - fix previous changes made to Annex H for introduction of non-ASCII support

*         Add cautionary language noting that implementations might only support ASCII/URIs?  Anything to note in Part 1?

2. Relative/absolute referencing

*         10-0015 - clarify "source part" for relationships

*         Add cautionary language about detailed interpretations of relative vs. absolute references as defined in RFC 3986?

3. Pack URI

*         09-0293 - decide how, and whether, to handle IANA registration

o   (see also historic info, including issues with Pack URI, here: http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml, http://www.iana.org/assignments/uri-schemes/historic/pack)

4. Digital signatures

*         11-0029 - is content from xmldsig-core duplicated in 13.2.4 (Digital Signature Markup)?

*         11-0030 - update normative reference to xmldsig-core?

*         11-0031 - update reference to xmlsec schema?

*         What, if anything, needs to be said about ensuring XAdES use is allowed?

5. Versioning

*         09-0168 - cannot distinguish between ECMA 1st ed OPC package and later versions (e.g., 29500 supports non-ASCII)

6. Editorial misc

*         12-0001 - unify capitalization of "relationship part"

*         Remove reference to Part 3 from clause 8 (Overview)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20140109/c364f236/attachment-0001.html>