Re: [cti] RFI & Motion: JSON MTI & JSON Schemas

["Jason Keirstead" <Jason.Keirstead@ca.ibm.com>]

I agree - but I would also propose that we do not vote on a normative spec, until there is an affiliated schema artifact attached, regardless of if that artifact is classified as informative or not.

We need to make sure that the normative text is practical and implementable. Without a spec showing how to implement the text, we have a large possibility of future problems.

IE - a JSON Schema should be a pre-requisite of voting on the specification.

-
Jason Keirstead
STSM, Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security | www.securityintelligence.com

Without data, all you are is just another person with an opinion - Unknown


John-Mark Gurney ---04/12/2016 01:14:38 PM---Wunder, John A. wrote this message on Mon, Apr 11, 2016 at 11:23 +0000: > Another comment is that I’

From: John-Mark Gurney <jmg@newcontext.com>
To: "Wunder, John A." <jwunder@mitre.org>
Cc: Aharon Chernin <achernin@soltra.com>, Patrick Maroney <Pmaroney@Specere.org>, OASIS CTI TC Discussion List <cti@lists.oasis-open.org>
Date: 04/12/2016 01:14 PM
Subject: Re: [cti] RFI & Motion: JSON MTI & JSON Schemas
Sent by: <cti@lists.oasis-open.org>

---

Wunder, John A. wrote this message on Mon, Apr 11, 2016 at 11:23 +0000:
> Another comment is that I’ve seen people using the term “normative” in relation to the schemas. I used to think the schemas would be normative too but was convinced otherwise. Schemas should be informative…that way you can resolve disagreements between the schemas and the text specifications in favor of the text specifications and ensure consistency across all of the serializations (MTI and otherwise). This is how MITRE has done other specs as well, and is how TAXII 1.1’s XML Binding Specification is written.

I agree, the spec is the only normative definition.  The schema helps
validate adherence to the spec, but the schema should not be considered
normative..  It is possible that the schema cannot be as strict as the
specification says, so therefore the specification must be the final
arbiter..

-- 
John-Mark

---------------------------------------------------------------------
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