Forwarded from Gary Ham having issues with email address. Elysa From: Gary Ham [mailto:
garyham@grandpaham.com] Sent: Tuesday, October 6, 2015 11:00 AM To: Elysa Jones <
elysajones@yahoo.com> Cc:
emergency@lists.oasis-open.org Subject: Re: [emergency] Packaged CAP The message content is a CAP message. The feed is not strictly a “CAP Feed.” OTOH the feed can be defined as a feed of DE wrapped CAP content. As to whether it can be expressed as a news feed, of course it can, but so can any XML, even non standard data. And if someone want to express the results as a CAP feed instead of a DE feed of wrapped CAP content, that can build one. XSLT is pretty fast. I find the argument to be trivial semantics, but I agree that it should not be labeled “CAP feed” by itself with no qualification in the name. But if the Content is reliably CAP, then CAP can be used in the name of the feed with appropriate identification that it is the content, not the wrapper. The same would apply to CoT wrapped CAP, or CAP inside a ebXML wrapper. or……... vr, Gary Ham (CTR) Contractor via ArcAspicio FEMA/NCP IPAWS Systems Architect, IPAWS-OPEN Mobile Phone: 703-899-6241 e-mail:
garyham@grandpaham.com On Oct 6, 2015, at 11:15 AM, Elysa Jones <
elysajones@yahoo.com > wrote: Friends, After CAP workshop in Rome, the following link was sent to me:
http://www.rfs.nsw.gov.au/feeds/majorIncidentsCAP.xml with the question - is this a CAP message? Our friend Eliot Christian adamantly says NO – it cannot be expressed as a news feed and time will be wasted and lives can be lost while critical information is being unpacked. However, if you look at the contents of the DE shown, valid CAP is there packaged nicely in the DE 1.0. What are your thoughts? Best regards, Elysa Jones, Chair OASIS EM-TC