RE: [energyinterop] Background re: steps for Energy Interoperation forwarding to the IEC

["Holmberg, David" <david.holmberg@nist.gov>]

All,

 

Thanks for a productive meeting today as we looked at options for advancing EI to IEC. We focused in on “option b” of the three options offered to us by OASIS, and Bill sent around a draft agreement and will update that and circulate again for TC review. The update based on feedback will be what we vote on at our July 9 TC meeting. As Toby noted on the call, there may be some back and forth with IEC, but the plan we discussed (and also as we discussed in IEC PC118 meetings) is that OASIS will provide EI to IEC PC118 WG1 to become a Committee Draft. Our next PC118 meeting is in September in Singapore, and the goal there will be to put the EI spec out for comment, then address those comments with the goal of moving EI to international standard status with a minimum amount of technical changes. The OASIS goal is to avoid forked standards, and the goal is that EITC work cooperatively with PC118 to meet the needs of the world, with the same document published by OASIS as IEC. The EI submission agreement between OASIS and IEC will spell out how to make that cooperation work while maintaining efforts in both OASIS and IEC.

 

For now,

David

 

From: energyinterop@lists.oasis-open.org [mailto:energyinterop@lists.oasis-open.org] On Behalf Of William Cox
Sent: Wednesday, July 02, 2014 10:07 AM
To: EITC
Subject: [energyinterop] Background re: steps for Energy Interoperation forwarding to the IEC

 

All --

To guide our discussion at our Workshop meeting this week and Regular meeting next week, I'm forwarding an email from Jamie Clark, OASIS' liaison chair, with wording from a recent forwarding agreement.

This gives the context, and OASIS' requirement to avoid forking the specification. I've emboldened the context-setting paragraph below.

I've also attached the recently approved ebXML request to forward their specifications to ISO as another example.  The direct URI is https://www.oasis-open.org/committees/download.php/52622/ebXML-submission-request-v4.pdf ; document is attached.

Thanks!

bill

-------- Original Message --------

Subject:	Re: FW: Next steps for Energy Interoperation forwarding to the IEC
Date:	Fri, 27 Jun 2014 08:06:25 -0700
From:	Jamie Clark <jamie.clark@oasis-open.org>
To:	William Cox <wtcox@coxsoftwarearchitects.com>, "Holmberg, David" <david.holmberg@nist.gov>
CC:	Chet Ensign <chet.ensign@oasis-open.org>

 

David and Bill:

We deal with those kinds of issues in a "terms of submission" statement in our transmittals of submitted standards. (Separate "liaison agreements" or similar tend not to be a good vehicle for addressing the editing and licensing details of shared technical work.)

When OASIS sends a standard to an ISO, IEC or similar committee for its subsequent separate approval, we have (roughly) three options:  (a) limited permission to re-publish the whole thing, as is, only;  (b) permission to re-publish as-is, plus a commitment to mutually circulate and exchange approvals of any recommended changes, keeping a final revised version in lockstep so that both entities finally approve the same thing;  and (c) unlimited permission to take over editing and control all future versions.  Options (a) or (b) are appropriate to OASIS TCs who intend to continue working on the artifact;  option (c) is appropriate if an OASIS TC plans to close its work, and wholly turn over the pen to the recipient org.

(We're constrained to those choices because, as a policy matter, our rules require us to avoid unexpected forking -- where the OASIS TC might be working on a version 2 at the same time the exernal recipient is working on a *different* version 2, leading to confusion over which is the authorized and licensed version.)   

 

Attached is an example of option (b).  We used this approach on, among other things, the well-known and successful OpenDocument standard.  It resulted in several back-and-forth rounds between the OASIS TC and the recipient body, which served as an excellent vehicle for further improvements and collaboration on the eventual, co-published final artifact.

 

Cordially  JBC

   
James Bryce Clark, General Counsel
OASIS: Advancing open standards for the information society
http://www.oasis-open.org/who/staff.php

William Cox <wtcox@coxsoftwarearchitects.com> wrote:

Jamie -

Do you have samples of as-used liaison agreements?

Are the liaison agreements publicly visible? (https://www.oasis-open.org/liaisons has descriptions but not the agreements.

Is the IEC PC118-OASIS liaison listed there as "IEC"?

Thanks!

bill
--

William Cox 

Email: wtcox@CoxSoftwareArchitects.com 

Web: http://www.CoxSoftwareArchitects.com 

+1 862 485 3696 mobile 

+1 908 277 3460 fax