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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

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

Subject: Re: [emergency-comment] CAP support for Common InformationSharing Standard for Information Securit

I think Tim may have pointed us (at long last!) toward the correct approach to this recurrent concern.  

As I read it, this could be implemented to allow standardized attributes for classification level and other markings to be inserted in the <alert> tag to classify an entire message, or in an individual <info>, or even potentially at the level of other specific elements such as <parameter> or <resource>.  (It does depart from our traditional preference for elements over attributes, but given the inherently limited domain of these extensions I'm not sure that would cause much of a problem.)

I'm assuming that DHS, DoJ and IC usages are aligned with DoD practice here.  However, if other agencies (or other nations) needed to develop their own comparable schemas, it seems like those could be included as well, with or without our mandate.

Maybe some of our schema experts can double-check my understanding here.

- Art

Art Botterell, Manager
Community Warning System
Contra Costa County Office of the Sheriff
50 Glacier Drive
Martinez, California 94553
(925) 313-9603
fax (925) 646-1120

>>> <Timothy_Dunlevy@emainc.com> 5/20/2009 12:58 PM >>>
I am the Chief SOA Architect for several DoD projects. One of these
uses CAP v1.1 as the primary data representation for receipt and
transmission of alerts.

We have additional requirements to use the 'Common Information Sharing
Standard for Information Security Marking: XML Implementation' from the
Office of the Director of National Intelligence Chief Information
Release 2.0.3 dated 15 February 2006.

It would be a great advantage to include the above ISM extensions in the
schema. Is there any possibility of incorporating these extensions into

Currently, we are using the <scope> and <restriction> elements in CAP to
contain this information but having the attributes defined by ISM
in the CAP schema would make processing CAP much simpler for the entire


Tim Dunlevy

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: emergency-comment-subscribe@lists.oasis-open.org 
Unsubscribe: emergency-comment-unsubscribe@lists.oasis-open.org 
List help: emergency-comment-help@lists.oasis-open.org 
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 

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