[OASIS Issue Tracker] Created: (SOAEERP-17) PR08-T1 WhitePaper-cd03 Section: *Conceptual Framework and Message Flow*

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

                 Key: SOAEERP-17
                 URL: http://tools.oasis-open.org/issues/browse/SOAEERP-17
             Project: OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
          Issue Type: Sub-task
          Components: PR Comments
            Reporter: Paul Yang 


    * 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). 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira