[OASIS Issue Tracker] Issue Comment Edited: (EMFW-3) DE 2.0 Schema Cleanup Issue- XLink -namespace collision

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

    [ http://tools.oasis-open.org/issues/browse/EMFW-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30326#action_30326 ] 

Martena Gooch edited comment on EMFW-3 at 5/8/12 10:18 AM:
-----------------------------------------------------------

Should we convert to using the latest official W3C Xlink
schema?

Yes. Adoption of the latest W3C Xlink schema will help
standardization and help to avoid double importing of Xlink and avoid the
need for the additional xlink schema found in earlier versions of the draft
DE 2.0 schema. The challenge is that some of the attribute names or group
names have changed and the new official schema uses the same namespace as
the older schema we and related EDXL standards, like Hospital Availability
and GML Simple Features Profile, were using. Consequently, there remain
double-import issues until those schema are updated.

Reference: 05-01-12-Minutes-IF-Subcommittee Meeting Notes 

      was (Author: goochm@saic.com):
    Should we convert to using the latest official W3C Xlink
schema?

Yes. Adoption of the latest W3C Xlink schema will help
standardization and help to avoid double importing of Xlink and avoid the
need for the additional xlink schema found in earlier versions of the draft
DE 2.0 schema. The challenge is that some of the attribute names or group
names have changed and the new official schema uses the same namespace as
the older schema we and related EDXL standards, like Hospital Availability
and GML Simple Features Profile, were using. Consequently, there remain
double-import issues until those schema are updated.


  
> DE 2.0 Schema Cleanup Issue- XLink -namespace collision
> -------------------------------------------------------
>
>                 Key: EMFW-3
>                 URL: http://tools.oasis-open.org/issues/browse/EMFW-3
>             Project: OASIS EDXL Distribution Element
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: csprd01 - Public Review Draft #1
>         Environment: Mitre-Don McGarry
>            Reporter: Martena Gooch
>            Priority: Minor
>             Fix For: csprd01 - Public Review Draft #1
>
>
> XLink was double-imported which caused a namespace collision...This statement needs to be commented out of edxlgsf base or other files 
> <import namespace="http://www.w3.org/1999/xlink"; schemaLocation="http://schemas.opengis.net/xlink/1.0.0/xlinks.xsd"/>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira