[OASIS Issue Tracker] Created: (ENERGYINTEROP-580) Additional Comments on Services Payloads

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

Additional Comments on Services Payloads
----------------------------------------

                 Key: ENERGYINTEROP-580
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-580
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: spec
            Reporter: Edward Cazalet 
            Assignee: William Cox
             Fix For: wd30



Question:  if a service is delivered to an URL ( IP address) then the payload also needs to identify the the parties to the service?  Perhaps I don't fully understand how the services will be defined.

For example, EiCreateTender should have both the TenderorPartyID and the TendereePartyIDs.  URLs may change but the PartyIDs should not. 


Registration:

EiRegisterParty is just one example.  I suggest that the service be generic. EiRegister where what is registered can be a Party, EMIX Interface, Elements of an EMIX interface, EMIX MarketContext etc.  The Registrar normally will be a Party.
The purpose of registration is to assign unique IDs that may be used in different market contexts etc.

Enrollment:
Enrollment is Party in a MarketContext or Program (is this just a Market Context, or a sub Market Contact). Is suggest using the term EnrollAdmin instead of EnrollingParty.


Transaction Services:

EiRequest Transaction needs Party in addition to the CounterParty and the Requestor Party.  When permitted the requester may be a regulator or another authorized party not a party to the transaction.


Tender Services

I repeat my recommendation that Party and CounterParty be used instead of Tenderor and Tender.  The use of Party and CounterParty is clear in the context of a Tender and a Transaction and this usage has been in place for over a year in the TeMIX White Paper and throughout the Ei Specification.  In recent EI Specification drafts some UML diagrams proposed Tenderee and Tenderor but no TC consensus was attempted in my recollection.  Our terminology should be a simple as possible. 


Quote Services

I suggest the term publisherPartyID instead of quoterPartyID.


-- 
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