Stateless packet Filtering Comment: Compliance language should reflect the schema, not the property tables

["Brule, Joseph M" <jmbrule@radium.ncsc.mil>]

OpenC2 Technical Committee, 

Suggest the following substantive change to the "Open Command and Control (OpenC2) Profile for Stateless Packet Filtering Version 1.0"  

BACKGROUND: 
Currently section 3.1 on page 24 lines 19 and 40 of the pdf version of the SLPF states: "MUST support JSON serialization of OpenC2 commands that are syntactically valid in accordance with the property tables ..."

However, the opening paragraph of Annex A states "however in the event of a conflict between this annex, the property tables presented in section 2, and the separate plain text file listed below, the schema text file is authoritative" and in accordance with OASIS TC Process rules (section 2.2.5):  
" All normative computer language definitions must also be provided in separate plain text files;
Each text file must be referenced from the Work Product; and
Where any definition in these separate files disagrees with the definition found in the specification documentation, the definition in the separate file prevails." 

PROPOSED CHANGE: 
Modify the text in section 3.1 to read:  ": "MUST support JSON serialization of OpenC2 commands that are syntactically valid in accordance with the schema available at ..."

JUSTIFICATION: 
The tables are generated by the schema, so a conflicts will be infrequent (if at all).  Given that OASIS rules state the text files are authoritative and that we are focusing on a M2M specification, then it is logical to have the schema as the conformance criteria 

Respectfully Submitted,


Joe Brule