Thanks, Martin, for noticing this at
this early stage.
Peter, your comment included moving SOA-RA(F) from non-normative
to normative; from your email you have no opinion on the
placement, so we will keep it as non-normative as reviewed.
Chet, thanks for the wide distribution of the ballot notice so
Martin could notice the problem.
I have requested the following to ensure that only non-material
changes are included in the member ballot draft:
(1) That TC Admin terminate the present TC ballot referenced below
(2) That the Energy Interoperation TC editor (Toby) create a new
working draft based on wd41 with the following changes:
(a) Change any occurrences of the local reference
indicator/mark "[SOA-RAF]" to "[SOA-RA]" consistent with the
artifact name
(b) Ensure that the reference to SOA Reference Architecture
Framework tagged "[SOA-RA]" is non-normative
(c) Retain the XSD normative reference (non-substantive)
(d) Retain the Vavailability non-normative reference (no
change, update to current version)
(3) When the new working draft is ready, start a new ballot using
that working draft.
Comments and suggestions from Martin and other list subscribers
are welcome.
Thanks!
bill cox
co-chair, OASIS Energy Interoperation Technical Committee
--
William Cox
Email:
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax
On 5/16/14 7:38 PM, Considine, Toby wrote:
There
are a few matters in this ball of yarn. If we unravel them
in the wrong order, we will get confused, and fixate on the
wrong things. There is a trivial issue of typography that
the editor, blat him did not catch. That must be addressed
first.
(1)
Peter Brown submitted a comment that we should use the
released version rather than the draft version. This was
non-controversial. He then committed the kindness of
submitting what that reference should be. This submitted
reference flowed through at least one of the chairs,
multiple correspondences by the committee officers, and
through the editor and into the document. It was considered
non-substantive, because it was a correction to the final
rather than to the working draft.
I
can prepare a set of attachments with all the emails if
folks like, but for, I am asserting that this was
non-controversial, and can be traced. I state the entire
history because I will need to loop through it a few times.
(2)
In the comment submitted by Peter Brown, the “reference”
mark morphed from SOA-RA to SOA-RAF. This was odd, because
it actually points to an artifact named SOA-RA. Here is the
URI from WD41 that supports this.
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.pdf.
Whether this was an error or cut and paste, or whatever,
this changed “bookmark” flowed through the entire process
traced above.
The
editor recalls noting the change when reading the comment,
and things were still to be done tomorrow. “I’ll have to be
sure to catch that one, as it will break all the reference”.
Unfortunately, when it became “things to do today”, the
editor forgot all about it.
That
is the full and complete story of how we got an childless
reference whose children are never seen anywhere in the
document. It is also the tale of how the five references to
SOA-RA in the document became orphans.
Fixing
that error (changing the name of the reference back to what
is was originally) will require a WD41, but that is editing
and typography only.
(3)
Once that change is made, we have another separate issue.
Should the long-standing reference to SOA-RA (not SOA-RAF)
in the document be normative or non-normative. It was
non-normative initially. In part, this was because some on
the TC objected to a normative reference to a working draft.
I honestly believe we spent so little time on that issue
that no history can be reconstructed.
Peter
Brown’s comment put it in the Normative Section, and it
flowed through the process above. It is no longer a working
draft, so that seemed appropriate to all who discussed it. I
believe it is controversial now only because prior to making
the correction in (2), it appeared as if we had a normative
reference that was never used.
(4)
Care is good in a spec, and especially in something heading
(I hope) to be an OASIS standard. I note that no one
commented at all on the removal of one normative spec at the
same time set of edits.
VAVAILABILITY
was previously listed as both a Normative and a
Non-Normative reference. It is incorporated into the OASIS
specification WS-Calendar, but the TC felt that referencing
the draft RFC would make it easier for the implementer.
(5)
XSD is referenced and used throughout the document. XSD was
added as a normative reference.
(6)There
were several inconsistencies in the OASIS references, both
normative and non-normative, that were highlighted by Peter
Brown’s comment/submission. Those were all made consistent
with current recommendations as confirmed by TC-Admin.
Now,
having unraveled all the confusing noise, we have the simple
question, is moving the existing reference to SOA-RA from
Non-Normative to Normative, as suggested by Peter Brown’s
comment submitted during review, appropriate.
My
thinking is as follows:
a)
It
is no longer a rough draft
b)
It
is referenced multiple times in the document (mutatis
mutandis as above)
c)
The
language used in several of those references makes it appear
normative.
However:
d)
It
is not a hill I care to die on, or even stub my toe on
e)
If
someone wants to push it down, it matters little because
f)
1-6
will require a WD42 anyway.
tc
T
“The
single biggest problem in communication is the illusion that
it has taken place.”
–
George Bernard Shaw.
Toby
Considine
TC9, Inc
OASIS
TC Chair: oBIX & WS-Calendar
OASIS
TC Editor: EMIX, Energy Interoperation
SGIP
Smart Grid Architecture Committee
Email:
Phone: (919)619-2104
http://www.tcnine.com
blog: http://www.NewDaedalus.com
From:
[mailto:]
On Behalf Of Chet Ensign
Sent: Friday, May 16, 2014 4:44 PM
To: Peter F Brown; EITC; Martin Chapman
Cc: ;
Subject: [energyinterop] Re: [oasis-member-discuss]
FW: [members] A ballot to approve continuing with the
submission of Energy Interoperation V1.0 with Non-Material
Changes to an OS vote has been set up
Members of the Energy Interoperation TC,
Could I ask for a response to the
second concern that Martin has expressed. I think Peter
has answered the first question just fine but I do think
the non-normative/normative question needs to be
addressed.
Thanks very much for your attention,
/chet
On Fri, May 16, 2014 at 1:40 PM, Peter
F Brown <>
wrote:
Martin,
Chet
I
think that there are two distinct issues here:
-
There is no longer any artifact entitled ‘SOA-RA’
– this draft name was dropped a couple of years
ago in favour of ‘SOA-RAF’ as the work evolved.
Removing references to ‘RA’ is therefore the right
thing to do in this deliverable;
-
Shifting reference to the newly designated
‘SOA-RAF’ to being a normative rather than
non-normative reference.
I
think that the change in the title of the target
referenced is non-material, as it is simply a
reflection of the reality – that SOA-RA morphed to
SOA-RAF.
On
the separate issue as to whether changing such
reference from the non-normative to the normative
references section, I have no opinion.
Cheers,
Peter
From:
[mailto:]
On Behalf Of Martin Chapman
Sent: Friday, 16 May, 2014 06:54
To:
Subject: [oasis-member-discuss] FW:
[members] A ballot to approve continuing with
the submission of Energy Interoperation V1.0
with Non-Material Changes to an OS vote has
been set up
Chet,
I am always a bit concerned when
normative references get tinkered with. So I
checked through the document to see if the
changes were indeed non-material.
I am satisfied with all of the
changes except the two related to SOA-RA/F.
SOA-RAF has been added as a new
normative reference, yet it is not referred to
in the body of the document at all. This in
itself while bad practice would not
necessarily constitute a material change.
However, there was a non-normative reference
to [SOA-RA] , which is quoted throughout the
document, but this has been deleted. If the
intention was to replace the non-normative
[SOA-RA] reference with a normative reference
to [SOA-RAF] then this would be a Material
change IMHO. In any case, there are now two
inconsistencies that should be fixed prior to
OS. The non-normative reference to [SOA-RA]
needs to be reinstated and [SOA-RAF] deleted -
this will be non-material, or the [SOA-RA]
reference should be changed to [SOA-RAF] which
would be material since this is a new
normative reference.
I hope the TC will do the right
thing!
Regards,
Martin.
From:
Chet Ensign [mailto:]
Sent: 15 May 2014 23:02
To: ;
;
EITC
Subject: [members] A ballot to
approve continuing with the submission of
Energy Interoperation V1.0 with Non-Material
Changes to an OS vote has been set up
OASIS members,
The OASIS Energy
Interoperation TC members [1] have
requested a Special Majority Vote to
approve continuing with the submission of
Energy Interoperation Version 1.0 with
Non-Material Changes to an OASIS Standard
vote.
The TC received comments
during the public review of the Candidate
OASIS Standard (COS). Changes have been
made to the COS to address the comments
received. The description of the changes
can be inspected in the file named
energyinterop-1-0-spec-wd41-with-changes-cos01.pdf
in the complete ZIP archive of the Work
Product at
https://www.oasis-open.org/committees/document.php?document_id=53025&wg_abbrev=energyinterop.
The TC judges these changes
to be Non-Material in accordance with the
definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange).
The TC requested this ballot in accordance
with the procedures for handling comments
specified in section 3.4.2 Public Review
of a Candidate OASIS Standard of the OASIS
TC Process (https://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard).
The ballot can be inspected
at
https://www.oasis-open.org/committees/ballot.php?id=2611.
The ballot opens on 16 May
2014 at 00:00 GMT and closes on 22 May
2014 at 23:59 GMT.
- - - Additional information
[1] OASIS Energy
Interoperation TC
https://www.oasis-open.org/committees/energyinterop/
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC
Administration
OASIS: Advancing open standards for the
information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the
Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support
is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support
Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
