Fwd: Statements of Use

[Nuwan Waidyanatha]

Dominic et al,

If I remember correctly Eden had implemented DE 1.0 but not 2.0? Want
to clear with you all before replying to her.

Thanks
Nuwan


---------- Forwarded message ----------
From: Elysa Jones <elysa...@yahoo.com>
Date: Mon, Feb 8, 2016 at 7:32 PM
Subject: Statements of Use
To: Nuwan Waidyanatha <nu...@sahanafoundation.org>


Hi Nuwan,



I hope this note finds you doing well! It was great seeing you in
Rome and hearing about your work. Would Sahana be interested in
providing a “Statement of Use” for the DE 2.0? As an OASIS member
doing this, Sahana would get some good coverage on the site and also
in an article Robin Cover writes. IES is also going to provide a
statement which was posted to the list and worded as follows:



IES Solutions, technical coordinator of the IDIRA project
(www.idira.eu) has used EDXL-DE v2.0, CAP 1.2, EDXL-RM, EDXL-SitRept
in accordance with the mandatory conformance clauses specified therein
and OASIS policy. The work has been carried under the general
coordination of Fraunhofer-IVI and a group of 17 Partners from several
EU countries (Italy, Germany, Greece, Austria, UK, Czech Republic,
Switzerland).



If you are interested, we have the third one also lined up from a
non-OASIS member. With your statement, we should be able to start the
final OASIS Standard Ratification process with the three statements of
use.



Thanks,

Elysa Jones

[Fran Boon]

Correct:
https://github.com/flavour/eden/blob/master/static/formats/edrm/export.xsl#L3

On 8 February 2016 at 14:08, Nuwan Waidyanatha

> --
> You received this message because you are subscribed to the Google Groups "standards" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to standards+...@sahanafoundation.org.
>

[Nuwan Waidyanatha]

Thanks Fran!

We do have DE 2.0 in the horizon with the SAMBRO administrator defined
first-responder alerting. Within our curreent scope of that work flow,
DE 2.0 is not essential; however, if we did require interoperating
with a third party to distribute the CAP payload, it might come in
handy?