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-69) TEP 1.1 - TAB-1341: 5 Conformance - lack of specifics

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

Patti Aymond commented on EMERGENCY-69:

Reporter: Patrick Durusau

> TEP 1.1 - TAB-1341: 5 Conformance - lack of specifics
> -----------------------------------------------------
>                 Key: EMERGENCY-69
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-69
>             Project: OASIS Emergency Management TC
>          Issue Type: Bug
>          Components: TEP
>         Environment: Conformance
>            Reporter: Patti Aymond
>            Assignee: Patti Aymond
> 5 Conformance reads in part: 
> " c) if its namespace name is "urn:oasis:names:tc:emergency:edxl:tep:1.0", then its content (which includes the content of each of its descendants) meets all the additional mandatory requirements provided in the specific subsection of Section 4 corresponding to the element’s name." 
> Given the questions about "must," "should," etc. that is a bit vague. 
> I don't recall seeing that many "additional mandatory requirements" beyond those of the schema (some co-occurrence constraints, etc.) so why not list them here with references (that's where the sections for elements would be handy). 
> It will insure that all implementers get the same set of "additional mandatory requirements" which will improve the odds of interoperability and more importantly, adoption.

This message was sent by Atlassian JIRA

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