Re: Possibility to describe name change of a person using xPIL?

[Ram Kumar <ram.kumar@oasis-open.org>]

Hi Ville,

The latest version of CIQ that will go for public review very soon has the
capabilities that you are looking for.

Regards,

Ram

Ville Paasimaa wrote:
> Hello,
>
> Thanks for your reply to my last email!
>
> We do have some further questions regariding to the xPIL spec:
>
> ============================================================================== 
>
> Issue 1) Marking the "information type" of the Address, Name, 
> ContactNumber and EmailAddress elements
>
> The issue is related to the following use-case:
> -a customer company A will submit Itella the party information of all 
> the users in the company's consumer user register
> -Itella will then check the names and addresses against Itella's 
> production databases and correct and update the data
> -Itella will send the corrected material back to the company A
>
> We would like the corrected material to include also original material 
> sent by the customer. The reason for it is that it helps the customer 
> to match the old info to the new changed info in their customer register.
>
> We would have 3 infoTypes for this purpose:
>
> infoType="OrigContactInfo" marking the original info sent by the customer
> infoType="NewContactInfo" marking that the customer should update the 
> original info they had with this new info that was found in Itella's 
> register
> infoType="AlternativeContactInfo"  marking the alternative contact 
> info that was available in Itella's register
>
> Please see the attached example!
>
> I studied to possibility to use the DataQuality attribute (and 
> DataQualityEnumeration) for this purpose , but the problem is that it 
> is not possible to set the data quality attribute to the root Address 
> element (but only to the sub elements of the Address, such as PostCode).
>
> ============================================================================== 
>
> Issue 2) Could it be possible to have similar extensible and 
> customizable typing mechanism for the usage attribute as well?
> It would be handy if the allowed values for the usage attribute of 
> Address could be enumerated in xAL-types.xsd and similarily for the 
> EmailAddresses and ContactNumbers in xPIL-types.xsd.
>
>
> I think I might come up with more questions and issues when I'll start 
> to produce a demo/proto application for our example use case. Hope my 
> questions
>
> t ville
>
> Ram Kumar wrote:
>> Hi Ville,
>> Yes, this change of party name (person or organisation) and even 
>> addresses of a party are captured by
>> CIQ including validity dates (date valid from and to). You have to 
>> make sure that the attribute value
>> "Current" and "Former" is defined in the enumeration list which is a 
>> separate file (xNL-types.xsd).
>>
>> Please let me know what issue you have with the current specs., that 
>> cannot meet your requirements.
>>
>> We will be releasing v3.0 of CIQ for public review very soon.
>>
>> Looking forward to hearing from you,
>>
>> Regards,
>>
>> Ram
>>
>> Ville Paasimaa wrote:
>>> Hi Ram!
>>>
>>> I'm still evaluating the possibilities to use the xPIL, xAL, xNL in 
>>> Posti Finland Corporation. By the way, the name of Posti Finland 
>>> Corporation will chage to Itella in near future.
>>>
>>> Our use-cases are related to contact information exchange between 
>>> different contact information registers and Itella. Typical 
>>> situation is that a customer company will submit us a contact 
>>> information of all the customers in their consumer user register. 
>>> Itella will then check the names and addresses against our databases 
>>> and correct and update them and send the corrected material back to 
>>> the customer. One situation is that a name of the some consumer has 
>>> changed. We would like to submit back to the customer company the 
>>> former name of the consumer user and the current (or new) name of 
>>> the consumer user.
>>>
>>> Here is an Example scenario:
>>>
>>> A person has changed her name from Kirsi Tuovinen to Kirsi Paasimaa
>>>
>>> I would need something like this to describe it in XML:
>>>
>>> <p:Party>
>>>   <n:PartyName>
>>>     <n:PersonName p:Type="Current">
>>>       <n:NameElement n:ElementType="FirstName">Kirsi</n:NameElement>
>>>       <n:NameElement n:ElementType="LastName">Paasimaa</n:NameElement>
>>>     </n:PersonName>
>>>     <n:PersonName p:Type="Former">
>>>       <n:NameElement n:ElementType="FirstName">Kirsi</n:NameElement>
>>>       <n:NameElement n:ElementType="LastName">Tuovinen</n:NameElement>
>>>     </n:PersonName>
>>>   </n:PartyName>
>>> </p:Party>
>>>
>>> br,
>>>
>>> Ville
>>>
>>
>
> ------------------------------------------------------------------------
>
> -a customer company A will submit Itella the party information of all the users in the company's consumer user register
> -Itella will then check the names and addresses against Itella's production databases and correct and update the data 
> -Itella will send the corrected material back to the company A
>
> We would like the corrected material to include also original material sent by the customer. The reason for it is that it helps the customer to match the old info to the new changed info in their customer register.
>
> We would have 3 infoTypes for this purpose:
>
> infoType="OrigContactInfo" marking the original info sent by the customer
> infoType="NewContactInfo" marking that the customer should update the original info they had with this new info that was found in Itella's register
> infoType="AlternativeContactInfo"  marking the alternative contact info that was available in Itella's register
>
> <example content removed by OASIS Administration>

-- 
Ram Kumar
Manager - Technical Committee Development
OASIS
Post Office Box 455
Billerica,MA 0821
USA
+61 412 758 025 (Direct)
+ 1 978 667 5115 (OASIS HQ)
+ 1 978 667 5114 (Fax)
ram.kumar@oasis-open.org
http://www.oasis-open.org
"Advancing e-Business Standards Since 1993"