OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]