PR08-T1 WhitePaper-cd03 Section: *Conceptual Framework and Message Flow*

XMLWordPrintable

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

      WD09 of Whitepaper, http://www.oasis-open.org/committees/download.php/38426/EERP-Model-UseCase-WhitePaper-wd09-diff-cd03-withLineNumber.pdf , Line 233-227 has the following:

      223 Note that this conceptual framework is just one way of implementing the EERP
      224 technology. There are alternate ways to implement EERP without the EERP Portal. For
      225 example, one could use the ebXML Registry/Repository or similar means to exchange
      226 business quality of services information, and begin negotiations for establishing Business
      227 Service Level Agreements (bSLAs).

      Show
      WD09 of Whitepaper, http://www.oasis-open.org/committees/download.php/38426/EERP-Model-UseCase-WhitePaper-wd09-diff-cd03-withLineNumber.pdf , Line 233-227 has the following: 223 Note that this conceptual framework is just one way of implementing the EERP 224 technology. There are alternate ways to implement EERP without the EERP Portal. For 225 example, one could use the ebXML Registry/Repository or similar means to exchange 226 business quality of services information, and begin negotiations for establishing Business 227 Service Level Agreements (bSLAs).
    • Hide

      WD09 of Whitepaper, http://www.oasis-open.org/committees/download.php/38426/EERP-Model-UseCase-WhitePaper-wd09-diff-cd03-withLineNumber.pdf , Line 233-227 has the following:

      223 Note that this conceptual framework is just one way of implementing the EERP
      224 technology. There are alternate ways to implement EERP without the EERP Portal. For
      225 example, one could use the ebXML Registry/Repository or similar means to exchange
      226 business quality of services information, and begin negotiations for establishing Business
      227 Service Level Agreements (bSLAs).

      Show
      WD09 of Whitepaper, http://www.oasis-open.org/committees/download.php/38426/EERP-Model-UseCase-WhitePaper-wd09-diff-cd03-withLineNumber.pdf , Line 233-227 has the following: 223 Note that this conceptual framework is just one way of implementing the EERP 224 technology. There are alternate ways to implement EERP without the EERP Portal. For 225 example, one could use the ebXML Registry/Repository or similar means to exchange 226 business quality of services information, and begin negotiations for establishing Business 227 Service Level Agreements (bSLAs).

      • Note: It appears that an EERP Portal is required. Is this so? If
        so, please explain why in this section. This could be more than
        some smaller service providers are willing or able to afford, and
        requiring third party facilities could be problematic--though I am
        personally requiring a similar third party facility in a Network
        Centric Pattern (NCP) in the Network Centric Operations Industry
        Consortium (NCOIC) All Hazards Alert and Warning Capabilities
        (AHAW) NCP in the form of a SOA Registry-Repository for Service
        Providers and Consumers to find each other, share Service
        Descriptions and acquire the contact information necessary to
        begin negotiations for establishing Service Level Agreements (SLAs).

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

              Created:
              Updated:
              Resolved: