DE 2.0 Schema Cleanup Issue- XLink -namespace collision

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Affects Version/s: csprd01 - Public Review Draft #1
    • Component/s: Schema
    • None
    • Environment:

      Mitre-Don McGarry

    • Hide

      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.

      Show
      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.

      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"/>

            Assignee:
            Unassigned
            Reporter:
            Martena Gooch (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: