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-97) TEP 1.1 - TAB-1329: Lack of namespace declarations in schema

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

Patti Aymond commented on EMERGENCY-97:

Reporter: Patrick Durusau

> TEP 1.1 - TAB-1329: Lack of namespace declarations in schema
> ------------------------------------------------------------
>                 Key: EMERGENCY-97
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-97
>             Project: OASIS Emergency Management TC
>          Issue Type: Bug
>          Components: TEP
>         Environment: References
>            Reporter: Patti Aymond
>            Assignee: Patti Aymond
>            Priority: Critical
> Assuming corrections mentioned in TAB-1328 are made, the schema lacks namespaces "declared in the prose specification." 
> The schema invokes/declares TEP, ct, xal, edxl (if corrected) 
> 4 Data Dictionary, some distance from its start, says: "Namespace prefixes: we use the following prefixes for namespace scoping of elements and types" 
> Which includes xsd, tep, and tep-ct, which don't appear in the schema. 
> BTW, if you want ext to stand for the namespace urn:oasis:names:tc:emergency:edxl:extension:1.0, it really has to occur in the schema. Can be mentioned in the prose but it must appear in the schema. 
> The document and the schema MUST agree on the namespaces and if you are declaring these, make sure they appear on the cover page as well.

This message was sent by Atlassian JIRA

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