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: [OASIS Issue Tracker] (EMERGENCY-12) UIDs for info blocks

    [ https://tools.oasis-open.org/issues/browse/EMERGENCY-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37636#comment-37636 ] 

Norm Paulsen commented on EMERGENCY-12:

We in Canada update them all. We have a pararmeter in the block that basically indicates "no change here",  or,  what the minor change is for the block the parmater is in (there are 6 types). So this parameter declares the nature of the change. This is only for non substantial changes as anything substantial is a full Update.

For consumers that use continuous signalling (web pages, cell broadcast, road side signs, crawlers, etc...) the new one will look like the old one so go ahead and process. From the audience point of view, the minor change would show up only for the display using the info block where the change happened.

For consumers that use instantaneous signalling (text, email, etc...) they can ignore the minor change except for the change type they are interested in, if any. The one we use a lot is "text" where text now appears in the <description>  element where it wasn't there before (Note: by federal policy we have to delay free form text in one language until its available in both. Since we have some free form text we have this delay).

Since this approach conforms to the "Wipe and replace" nature of CAP there is no need to ID an info block in our opinion. Markers in the block are used to decide if the block is to be processed or not. 

> UIDs for info blocks
> --------------------
>                 Key: EMERGENCY-12
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-12
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Is there a need for internally unique identifiers for info blocks? Intended to allow corrections to a single info block.

This message was sent by Atlassian JIRA

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