Public review - CAM evaluation of CAP 1.2 NIEM alignment.

["David RR Webber \(XML\)" <david@drrw.info>]

Team,

Feedback on NIEM conformance.

Suggest adding version="1.2" attribute to XSD schema to indicate version 1.2 as per NIEM.

Also W3C types should be qualified with xs: namespace prefix - currently they are not. E.g. xs:string, xs:date, etc.

Similarly all globally used types should be annotated and named.

Also WRT NIEM naming and design rules (NDR) the following report below is indicated by the CAM NDR evaluator tool for this (provides a selection of priority checks that are part of NIEM NDR also).  The addition of missing annotations to the XSD is obviously low hanging fruit (these can be extracted from the spec' documentation).

In addition attached is HTML documentation for the template use model overall - helps with assessment of the CAP 1.2 by providing a handy summary to crosscheck expected content and use (this is autogenerated from XSD annotations and rules).

Along with the Excel spreadsheet of the dictionary and comparison xref to NIEM dictionary.

Suggested enhancements to the XSD schema will aid use without necessarily changing the existing content model.

Thanks, DW

===================================================================================

CAM Template Evaluation

Version 1.15

CAM Template HEADER information:

Description:	Generated for alert by XSD 2 CAM generator v1.44
Owner:	To be Completed
Date:	2009-06-10T11:08:16
Version:	0.1

• Number of Elements: 54
• Number of Attributes: 0
• Number of constraint Rules: 69
• Annotations: 1
• Hints: 0
• Excluded Elements: 0
• Excluded Attributes: 0

RULES INTEGRITY:

• No problems found

NAMING AND DESIGN RULES (NDR) ASSESSMENT:

• element name does not match representation term rules: 10
  - sent - status - scope - category - urgency - severity - certainty - effective - onset - expires
  
• elements missing annotation description: 12
  - sent - status - msgType - scope - category - responseType - urgency - severity - certainty - effective - onset - expires
  
• element names not beginning with upper case letter (A-Z): 12
  - category certainty effective expires msgType onset responseType scope sent severity status urgency
  
  SCORE: 8.5 out of 10.0
  HINT: representation terms use indicates the nature of the value carried by a leaf node in the structure. The terms qualify the name of the node and its content.
  Representation terms are domain applicable and can be tailored accordingly. The default list of terms provided for guidance here are for a name that contains: 'Amount', 'Count', 'BinaryObject', 'Graphic', 'Picture', 'Sound', 'Video', 'Code', 'Category', 'Currency', 'EMail', 'DateTime', 'Date', 'Time', 'Indicator', 'Format', 'Length', 'Height', 'Width', 'Level', 'Measure', 'Mode', 'Method', 'Numeric', 'Number', 'Price', 'State', 'Status', 'Flag', 'Frequency', 'Format', 'Size', 'Unit', 'Value', 'Version', 'Rate', 'Required', 'Percent', 'Quantity', 'Qty', 'Description', 'Instructions', 'Text', 'Title', 'Type', 'Year', 'Month', 'Day', 'Name', 'URI', 'URL', or 'URN';
  or that ends with 'Days', 'Hours', 'Minutes', 'ID', 'Id', or 'Identifier'
  A domain may use specialized terms that are not in the overall list shown here.

ISSUES AND WARNINGS:

• Warning - code, type or flag items with no allowed values restriction
  • /cap:alert/cap:code
  • /cap:info/cap:eventCode
  • /cap:resource/cap:mimeType
  • /cap:area/cap:geocode

EXTERNALS:

Namespace

URL

CAP-v1.2-PR01-content.zip