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-3) Process to approve ASN format

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

Art Botterell commented on EMERGENCY-3:

We might actually want to consider starting with JSON, as arguably the simplest encoding and the one (currently) closest to bare data structure.  (Not looking to start a religious debate but the young software engineers I've been hanging out with are all about JSON.)

Indeed, in recent implementations I've done almost all the processing of CAP alerts in JSON format and only transformed them to XML at the system edge.  I'd do the same to ASN.1 if that requirement arose.

In any event, I'll be suggesting formalization of a JSON encoding as a separate issue.  (The OASIS position on JSON is set forth at https://www.oasis-open.org/resources/topics/rest-json.)

If anyone needs a quick refresher on JSON one resource is at http://www.elated.com/articles/json-basics/.

> Process to approve ASN format
> -----------------------------
>                 Key: EMERGENCY-3
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-3
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP

This message was sent by Atlassian JIRA

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