• Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • cd04
    • Affects Version/s: cd03
    • Component/s: PR01 Comments
    • None
    • Hide

      Requires delivery and approval of CD04. Needs to be applied as part of publication of that CD as a public review document.

      Show
      Requires delivery and approval of CD04. Needs to be applied as part of publication of that CD as a public review document.

      Following is the comments from Eclogue Chang on 3/18/2010:

      The SLA namespace page at http://docs.oasis-open.org/ns/soa-eerp/sla/200903爃as a broken link on EERP-SLA.xsd. It points to http://docs.oasis-open.org/soa-eerp/eerp-sla/200903/eerp-sla.xsd which will return 404 – Page燦ot Found error.

      Where is the SLA schema located?

      Eclogue Chang
      email: [email protected]

      ————————————————————————————————————————————————
      Szu's reply to this Eclogue Chang on 3/20/2010:

      Eclogue,
      Thanks for your comments. EERP-SLA.xsd can be found at
      http://docs.oasis-open.org/soa-eerp/sla/v1.0/EERP-SLA-cd03.xsd.
      There is a typo on the namespace page
      http://docs.oasis-open.org/ns/soa-eerp/sla/200903, and will be fixed soon.

      ___________________________________________________________________________________
      Eclogue Chang's response on 3/29/2010:

      Thanks for the reply on the SLA Schema location. Howver, when I tried to open the the schema at http://docs.oasis-open.org/soa-eerp/sla/v1.0/EERP-SLA-cd03.xsd聽with my XML editing tool to veiw the schema, I got the following error:

      "SchemView is unable to load following schema(s):
      http://docs.oasis-open.org/soa-eerp/eerp-bqos/200903/eerp-bqos.xsd"

      Looks like it is a problem on the SLA Schema.

            Assignee:
            Szu Chang (Inactive)
            Reporter:
            Paul Yang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: