Where specificity in serializations matters is Interoperability Testing, and rules for Interoperability Testing. The value in that regard is that the testing
focuses industry to work together – whether as a plugfest or full on Interop testing.
The goal being that with a limited but reasonable number of methods available so that development and fielding by Industry feasible with the desired results of
interoperability.
Thanks!
Chuck
From: openc2@lists.oasis-open.org [mailto:openc2@lists.oasis-open.org]
On Behalf Of Kemp, David P
Sent: Tuesday, October 17, 2017 3:54 PM
To: openc2@lists.oasis-open.org
Subject: [openc2] RE: [Non-DoD Source] RE: [openc2] Question about Sept meeting minutes
Allan,
I agree completely with your wording: “The JSON mapping of the Language Specification is a normative specification for the JSON implementation of OpenC2.”
That supplements but does not replace the existing: “The property tables in the Language Specification are normative.” That means that an implementation of any
other serialization (such as XML or Protobuf) of the Language Specification must also conform to the property tables, because the property tables apply equally to all serializations.
Dave
iPhone, iTypo, iApologize
-------- Original Message --------
Subject: Re: [openc2] Question about Sept meeting minutes
From: Allan Thomson <athomson@lookingglasscyber.com>
Date: Sun, October 15, 2017 3:58 pm
To: "duncan@sfractal.com" <duncan@sfractal.com>,
"openc2@lists.oasis-open.org" <openc2@lists.oasis-open.org>
Duncan – I suggest that it is much simpler to just state that the
JSON mapping of the Language Specification is a normative specification for the JSON implementation of OpenC2.
There is no reason why the spec needs to state that other mappings are possible as the free-market allows that to occur whether you write it in a spec or not.
We are not precluding anyone implementing other mappings. But if you define OpenC2 in JSON then you *must* implement it according to the specification of that mapping.
The meeting minutes for the Sept OpenC2 TC state "JSON, as an encoding, is non-normative". I'm not sure if we used that exact wording - but even we did, I'm not
sure it was correct. I believe current consensus is that JSON is mandatory as minimum implementation but we are allowing for other optional serializations in the future. I believe the point being made at the time was we were trying to say that if you did use
JSON, you had to do it the way specified. The reason for the 'if' was the optional serializations, not that JSON was 'non-normative'. I propose the following change:
Delete "Json, as an encoding, is non-normative. However,"
"The property tables in the Language Specification are normative. If you elect to use Json, then it should be done in accordance with the json specified in the
Language Specification. The OpenC2 Language Specification permits the use of other encodings."
iPhone, iTypo, iApologize
-------- Original Message --------
Subject: [openc2] Groups - OpenC2 TC Minut es 20 Sept 2017 uploaded
From: Joyce Fai<jlfai@nsa.gov>
Date: Fri, October 13, 2017 4:43 am
To: openc2@lists.oasis-open.org
Submitter's message
Dear OpenC2 TC Members,
The minutes for the 20 September TC meeting is available for your review. We will vote to approve these minutes at our upcoming Wednesday, 18 October 2017 TC meeting (1100ET and 2100ET).
Looking forward to speaking to you then.
Best,
-- Ms. Joyce Fai
Submitter: Ms. Joyce Fai
Group: OASIS Open Command and Control (OpenC2) TC
Folder: Meeting Notes
Date submitted: 2017-10-13 01:42:40
|
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|