[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: PartyID (more)
Further to my last e-mail. Jamie >Date: Fri, 30 Mar 2001 23:21:29 -0800 >From: Duane Nickull <duane@xmlglobal.com> >Subject: Re: Some Party questions >To: Martin W Sachs <mwsachs@us.ibm.com> >Marty: > >While this notion is probably acceptable to some degree, I want to >point out the uses for the PartyID. > >1. PartyID is an element within the CPP which identifies the party or >organization to whom the CPP belongs. If a PArty has muyltiple CPP's >it is possible that they would use the same Party Identifier in each >CPP (after all - it is the same party). > >2. Since it is possible that a party might have 2 or more CPP's (for >different divisions or ???), it is necessary to know which CPP you are >referring to when proposing a CPA which the company is a party to. > >3. Unless the PartyID is different for each CPP document instance, it >will not be sufficient to uniquely identify a specific CPP document. >Therefore, the CPA negotiation will be in confusion becuase the CPA >examiner will not be able to determine if the CPA is legal within the >capabilities expressed in a certain CPP document. > >I therefore assert that the CPP document requires a Unique Idenifier if >it is to be used. > >Maybe this can be in the form of a urn:dunsID PLUS >companydivisionID therefore making each company responsible for >uniquely identifying its' own CPP's. In previous experience >however, I would suggest this may fail. Why? Simply becuase it can. > >Thoughts? > >Duane
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC