RE: [energyinterop] Registration and Party IDs

["Toby Considine" <Toby.Considine@gmail.com>]

Slight change of pace here – into the schemas

 

We seem to be congealing around “Registration is how you get a Party ID”

A VEN is identified by a PartyID

A VTN is identified by a PartyID

A Transactive [agent] is identified by a PartyID

 

Several Parties may be part of some larger entity. If the Parties are acting as VENs, we may call that larger entity a Customer.

-          A Customer is the business entity behind 1-to-many VENs that have a common relationship to the entity behind a VTN , each identified by a PartyID.

-          Is there a common entity behind multiple VTNs that should have an ID as well?

-          Is there a common entity behind multiple [agents] as well?

Parties have Roles: “Buyer” and “Seller”. Should we have a BuyerID and a SellerID instead of a CustomerID and “%%%”?

 

 

 

 

The eiParty is an existing type. The type consists of a partyID, a partyName, and a partyRole. Is this correct? Does it line up with the narrative above? If so, then it implies that a party enrolling  as both a VTN and as a VEN should have two PartyIDs. This does not feel correct.

 

Where does the eiParty fit in the Transactive world?

 

 

 

 

tc

 

 

 

---

"He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you."   - Fredrich Nietzche

---

Toby Considine TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com/ blog: www.NewDaedalus.com