[OASIS Issue Tracker] (EMERGENCY-40) The specification does not seem to target EDXL-HAVE processors, unlike other EDXL specifications

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Darrell O'Donnell commented on EMERGENCY-40:
--------------------------------------------

we should add a Conformance clause - looks quite simple - follow the EDXL-RM example.

> The specification does not seem to target EDXL-HAVE processors, unlike other EDXL specifications
> ------------------------------------------------------------------------------------------------
>
>                 Key: EMERGENCY-40
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-40
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: HAVE2
>         Environment: Conformance
>            Reporter: Darrell O'Donnell
>            Assignee: Darrell O'Donnell
>
> TAB-1227
> "Other EDXL specifications tell about processors of EDXL messages, e.g. the well-structured conformance Clause in: 
> http://docs.oasis-open.org/emergency/edxl-rm/v1.0/errata/EDXL-RM-v1.0-OS-errata-os.html#_Toc189182048 
> distinguishes messages and processors. Don’t we want to also define what is a conforming processor for EDXL-HAVE messages? 
> We should then have two conformance targets (message, processor) , and two different conformance clauses.” 
> "
> Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0 CSPRD01



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)