Re: [emergency-cap] CAP Errata contributions

Hi Jacob, hi everybody,

These look to me as if they would be substantive changes to the CAP spec. For example, #1 above - a size restriction where none had previously existed could potentially break existing applications.

Am I making more out of these than they are? If any of these would qualify as "Substantive Changes" - defined in the TC Process as "a change to an OASIS Standard that would require a compliant application or implementation to be modified or rewritten in order to remain compliant" - then they cannot be handled through an Errata.

Best,

/chet

On Fri, Jan 15, 2016 at 12:45 PM, Jacob Westfall <jake@jpw.biz> wrote:

Hi,
Here is the list of issues that need to be worked on for the CAP Errata and Practices Guide. Looking for volunteers to take on one or two of these issues and draft up the changes that are necessary to contribute to the Errata.
In JIRA, the issue tracker, I've added the Labels "Errata" and "Practices" to the applicable issues. So you can easily filter the list using those labels.

Errata

1. alert.info.event size restriction https://issues.oasis-open.org/browse/EMERGENCY-1
2. alert.info.instruction size restriction https://issues.oasis-open.org/browse/EMERGENCY-2
22. Modify responseType https://issues.oasis-open.org/browse/EMERGENCY-22
27. Change Headline length limit to 140 https://issues.oasis-open.org/browse/EMERGENCY-27
31. Clarify and standardize ways to cancel a CAP alert https://issues.oasis-open.org/browse/EMERGENCY-31
99. Prevent the use of binary for the SHA-1 hash of a resource digest https://issues.oasis-open.org/browse/EMERGENCY-99

Practices Guide

1. alert.info.event size restriction https://issues.oasis-open.org/browse/EMERGENCY-1
2. alert.info.instruction size restriction https://issues.oasis-open.org/browse/EMERGENCY-2
17. Add event expiration element https://issues.oasis-open.org/browse/EMERGENCY-17
25. Restrict use of multiple Infos to multi-lingual versioning https://issues.oasis-open.org/browse/EMERGENCY-25
27. Change Headline length limit to 140 https://issues.oasis-open.org/browse/EMERGENCY-27
28. Recommend specifying a time zone in all DateTime fields https://issues.oasis-open.org/browse/EMERGENCY-28
29. Single text field that summarizes multiple area descriptions https://issues.oasis-open.org/browse/EMERGENCY-29
31. Clarify and standardize ways to cancel a CAP alert https://issues.oasis-open.org/browse/EMERGENCY-31

--
Jacob Westfall <jake@jpw.biz>

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

emergency-cap message