← Prev in month ← Prev in thread
Next in thread → Next in month →

RE: [emergency-comment] Public review - CAM evaluation of CAP 1.2 NIEMalignment.

From
David RR Webber \(XML\) <>
Date
2009-06-11T18:58:02+00:00
ID
Thread
RE: [emergency-comment] Public review - CAM evaluation of CAP 1.2 NIEMalignment.
Jacob,

I did re-run the analysis - as I realized it skipped the cap: prefixed items (a little gotcha I missed on the first run) - this time the run analysed the complete schema.

 

Believe this should now be everything.

Thanks, DW

======================================
      CAM Template Evaluation
    
    
      Version 1.15
    
    
      CAM Template HEADER information:
    
    
      

        
          Description:
        
        
          Generated for alert by XSD 2 CAM generator v1.44
        
      

      

        
          Owner:
        
        
          OASIS Emergency TC
        
      

      

        
          Date:
        
        
          2009-06-10T11:08:16
        
      

      

        
          Version:
        
        
          1.2
        
      

    
    
      

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

      

      - cap:identifier - cap:sender - sent - status - 
      cap:source - scope - cap:restriction - cap:addresses - cap:code - 
      cap:note - cap:references - cap:incidents - cap:language - category - 
      cap:event - urgency - severity - certainty - cap:audience - cap:value - 
      effective - onset - expires - cap:headline - cap:description - 
      cap:instruction - cap:web - cap:contact - cap:resourceDesc - cap:size - 
      cap:uri - cap:derefUri - cap:digest - cap:areaDesc - cap:polygon - 
      cap:circle - cap:altitude - cap:ceiling

      

        elements missing annotation description: 49
      

      

      - cap:identifier - cap:sender - sent - status - 
      msgType - cap:source - scope - cap:restriction - cap:addresses - 
      cap:code - cap:note - cap:references - cap:incidents - cap:info - 
      cap:language - category - cap:event - responseType - urgency - severity 
      - certainty - cap:audience - cap:eventCode - cap:valueName - cap:value - 
      effective - onset - expires - cap:senderName - cap:headline - 
      cap:description - cap:instruction - cap:web - cap:contact - 
      cap:parameter - cap:resource - cap:resourceDesc - cap:mimeType - 
      cap:size - cap:uri - cap:derefUri - cap:digest - cap:area - cap:areaDesc 
      - cap:polygon - cap:circle - cap:geocode - cap:altitude - cap:ceiling

      

        element names not beginning with upper case letter (A-Z): 50
      

      

      - cap:addresses cap:alert cap:altitude cap:area 
      cap:areaDesc cap:audience cap:ceiling cap:circle cap:code cap:contact 
      cap:derefUri cap:description cap:digest cap:event cap:eventCode 
      cap:geocode cap:headline cap:identifier cap:incidents cap:info 
      cap:instruction cap:language cap:mimeType cap:note cap:parameter 
      cap:polygon cap:references cap:resource cap:resourceDesc cap:restriction 
      cap:sender cap:senderName cap:size cap:source cap:uri cap:value 
      cap:valueName cap:web 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', 'Rank', 'Flag', 'Frequency', 'Format', 'Size', 
        'Unit', 'Value', 'Version', 'Rate', 'Required', 'Percent', 'Quantity', 
        'Qty', 'Description', 'Comment', 'Reason', 'Location', '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:     
  

-------- Original Message --------

Subject: Re: [emergency-comment] Public review - CAM evaluation of CAP

1.2 NIEM alignment.

From: Jacob Westfall <>

Date: Thu, June 11, 2009 2:10 pm

To: 

Hi,

	Thanks for your comment submission David.  The zip file with supporting info will be very useful for review.  The CAP 1.2 Public Review period ends July 27, if you have any further comments or feedback on 1.2, please send them in.

-- 



--

-- 

This publicly archived list offers a means to provide input to the

OASIS Emergency Management TC.

In order to verify user consent to the Feedback License terms and

to minimize spam in the list archive, subscription is required

before posting.

Subscribe: 

Unsubscribe: 

List help: 

List archive: http://lists.oasis-open.org/archives/emergency-comment/

Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf

List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency
← Prev in month ← Prev in thread
Next in thread → Next in month →