i022 Performance:QualityAssertion

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: Major
    • cd04
    • Affects Version/s: cd03
    • Component/s: spec
    • None
    • Hide

      Proposal 1 2009-06-24

      SOA-EERP BusinessQualityOfService-v1.0-spec-WD05 is uploaded at
      http://www.oasis-open.org/committees/download.php/33062/BusinessQualityOfService-v1.0-spec-wd05.doc

      It fixed this issue on line # 329-331.

      It is proposed to close the issue with above changes.

      Proposal 2 2009-06-24

      Szu: We probably will not change the schemas, as we've already reviewed them. This is put to any element of quality.

      Rex: This is only intended to be the first of what I expect to be several such issues; I hope that others on the TC will think about the kinds of assertions. Bill: Name-Value pairs have similar issues.Rex:

      Action: i022 Keep open.

      Bill suggested we defer decisions on whether a fix goes into CD02, a WD, or some other versions; then we'll go back through. Our current target is a new WD that can become Committee Draft 02.

      Proposal 3 2009-09-02

      Per TC meeting on 09/02/2009, mark it to defer to post CD02. This issue will be addressed after CD02.

      Show
      Proposal 1 2009-06-24 SOA-EERP BusinessQualityOfService-v1.0-spec-WD05 is uploaded at http://www.oasis-open.org/committees/download.php/33062/BusinessQualityOfService-v1.0-spec-wd05.doc It fixed this issue on line # 329-331. It is proposed to close the issue with above changes. Proposal 2 2009-06-24 Szu: We probably will not change the schemas, as we've already reviewed them. This is put to any element of quality. Rex: This is only intended to be the first of what I expect to be several such issues; I hope that others on the TC will think about the kinds of assertions. Bill: Name-Value pairs have similar issues.Rex: Action: i022 Keep open. Bill suggested we defer decisions on whether a fix goes into CD02, a WD, or some other versions; then we'll go back through. Our current target is a new WD that can become Committee Draft 02. Proposal 3 2009-09-02 Per TC meeting on 09/02/2009, mark it to defer to post CD02. This issue will be addressed after CD02.
    • Hide

      This issue is discussed on 06/23/2010's TC meeting, with:

      Current WD09 @ http://www.oasis-open.org/committees/download.php/38435/SOA-EERP-bQoS-Specwd09-diff-cd03.pdf has the following (Line 337 to 344):

      [18:34] /bqos:BQoS/bqos:BQoSQualities/bqosropertyName
      338 Property name is a required element for the name in the name and value pair in the Property
      339 element. It uses bqosropertyNameType which is a cbc:NamType from UBL that has a optional
      340 languageID attribute for language code.

      [18:34] /bqos:BQoS/bqos:BQoSQualities/bqosroperty/bqosropertyValue
      349 The property value is an optional element for the value in the name and value pair in the Property
      350 element. It uses bqosropertyValueType which is a cbc:NamType from UBL that has a optional
      351 languageID attribute for language code.

      You can put any name-value onto BQoSQualities.

      While any quality name/value can be asserted by a Service Provider, there are three pre-defined names, one of which (bQOSPrice) is mandatory. We are not addressing issues of namespace management for qualities beyond the three pre-defined qualities.

      The following text is added to BQoS spec at http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/39310/SOA-EERP-bSLA-Spec-cd04.pdf:

      444 The BQoSQualities, the Quality elements for bQoS, describes additional properties and attributes for the
      445 service. While any quality name/value can be asserted by a Service Provider to represent the quality of
      446 the service, this specification is not addressing issues of namespace management for qualities beyond
      447 the three pre-defined EERP namespaces.
      [ Show » ] Szu Chang added a comment - 15/Sep/10 03:39 PM The following text is added to BQoS spec at http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/39310/SOA-EERP-bSLA-Spec-cd04.pdf: 444 The BQoSQualities, the Quality elements for bQoS, describes additional properties and attributes for the 445 service. While any quality name/value can be asserted by a Service Provider to represent the quality of 446 the service, this specification is not addressing issues of namespace management for qualities beyond 447 the three pre-defined EERP namespaces.

      Show
      This issue is discussed on 06/23/2010's TC meeting, with: Current WD09 @ http://www.oasis-open.org/committees/download.php/38435/SOA-EERP-bQoS-Specwd09-diff-cd03.pdf has the following (Line 337 to 344): [18:34] /bqos:BQoS/bqos:BQoSQualities/bqosropertyName 338 Property name is a required element for the name in the name and value pair in the Property 339 element. It uses bqosropertyNameType which is a cbc:NamType from UBL that has a optional 340 languageID attribute for language code. [18:34] /bqos:BQoS/bqos:BQoSQualities/bqosroperty/bqosropertyValue 349 The property value is an optional element for the value in the name and value pair in the Property 350 element. It uses bqosropertyValueType which is a cbc:NamType from UBL that has a optional 351 languageID attribute for language code. You can put any name-value onto BQoSQualities. While any quality name/value can be asserted by a Service Provider, there are three pre-defined names, one of which (bQOSPrice) is mandatory. We are not addressing issues of namespace management for qualities beyond the three pre-defined qualities. The following text is added to BQoS spec at http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/39310/SOA-EERP-bSLA-Spec-cd04.pdf: 444 The BQoSQualities, the Quality elements for bQoS, describes additional properties and attributes for the 445 service. While any quality name/value can be asserted by a Service Provider to represent the quality of 446 the service, this specification is not addressing issues of namespace management for qualities beyond 447 the three pre-defined EERP namespaces. [ Show » ] Szu Chang added a comment - 15/Sep/10 03:39 PM The following text is added to BQoS spec at http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/39310/SOA-EERP-bSLA-Spec-cd04.pdf: 444 The BQoSQualities, the Quality elements for bQoS, describes additional properties and attributes for the 445 service. While any quality name/value can be asserted by a Service Provider to represent the quality of 446 the service, this specification is not addressing issues of namespace management for qualities beyond 447 the three pre-defined EERP namespaces.

      Hi Everyone,

      (Note: I'll repeat this intro where it applies to the issues I bring
      up.) I have not had time to address these specs as I would have
      preferred, but as I am working through the process of diagramming the
      SOA Reference Architecture Foundation due to be released for Public
      Review in July (hopefully), I do have time to bring up a few
      crossover issues that will help align and coordinate the use of the
      RAF to develop specific, concrete solution architectures.

      This Issue applies to the BQoS Specification for the Performance category.

      I think we should include a formal mechanism for Service Providers to
      assert the specific Qualities of their services. Because this is
      something that I expect will evolve over time, I don't have
      suggestions at this time for specific subcategories of Quality. I
      think it would be wise to include this as a free text element at
      first. Later we may have subcategories that arise, but I wouldn't
      want to wait until we define those in order to get feedback from our
      audience on what they want to assert about their services.

      For instance, a conference management service might assert: "We
      deliver a high percentage of decision makers and decision
      influencers." This kind of assertion sets the foundation for a rating
      service to say something like, "Acme Conference Management delivered
      an audience for Conference X in which only 35% of attendees could be
      confirmed as decision makers."

      Because many Quality Assertions may be subjective (e..g. "a good time
      will be had by all"), without such an assertion, rating services and
      potential Service Consumers will not have a basis against which to
      evaluate services. The point is that even subjective Quality
      Assertions can be evaluated by ratings services, even if we can
      assign an objective unit of measure.

      By providing Service Providers with a BQoS:
      Performance:QualityAssertion, I think we can begin to make better
      assessments of services.

      Cheers,

      Rex

      Raised against / Related drafts
      EERP-bQoS revision: WD04
      Justification
      N/A
      Related Issues
      Origin
      Rex Brooks
      Owner
      Szu Chang

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

              Created:
              Updated:
              Resolved: