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-40) The specification does not seem to target EDXL-HAVE processors, unlike other EDXL specifications


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

Rex Brooks updated EMERGENCY-40:
--------------------------------

    Resolution: Resolved per issue as agreed by EM HAVE SC.

> 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: EDXL-HAVE-v2.0
>         Environment: Conformance
>            Reporter: Darrell O'Donnell
>            Assignee: Darrell O'Donnell
>              Labels: discuss
>
> 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)


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