Namespace location is wrong in at least one of the specifications

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: OBIX 1.1 WD39
    • Component/s: OBIX 1.1 Specification
    • None
    • Hide

      Toby to create new schema, put into obix lib, and mail to Craig.

      Then Craig to put into the doc.

      Show
      Toby to create new schema, put into obix lib, and mail to Craig. Then Craig to put into the doc.
    • Hide

      Toby to create new schema, put into obix archive, and mail to Craig. (XSD wd44 is final result)

      Then Craig to put into the doc.

      Show
      Toby to create new schema, put into obix archive, and mail to Craig. (XSD wd44 is final result) Then Craig to put into the doc.

      • The namespace location seems to be different for the core, than what is referenced in the encodings doc – not sure if that’s okay, or if one is (or both are) wrong:
      o core: http://docs.oasis-open.org/ns/obix/201410
      o encodings: http://docs.oasis-open.org/obix/ns/201312/schema (for the core spec), and http://docs.oasis-open.org/obix/ns/

      {short-identifier and version}

      (for the encodings spec)
      o at the least, I think a specific version needs to be used in the encodings spec, and this should be the same for the core as for the companion standards.

      Also, what should the xsi:schemaLocation be in the xml root object’s attributes? This seems unclear to me from what we have in the specification so far. A typical 1.0 obix server returns:

      <obj href="https://<ip-address>/obix/" is="obix:Lobby" xsi:schemaLocation="http://obix.org/ns/schema/1.0 /obix/xsd">

      which is not correct for 1.1, so what should it be?

        1.
        		 Namespace is not valid / does not match CS03 Sub-task Closed Toby Considine (Inactive)

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            Craig Gemmill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: