[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ciq] Fwd: Request for help...
While
#other is not ideal it would be better than extending the schema IMHO. At
least there is a chance of ‘out of the box’ interop, whereas a schema extension
makes that less likely. It’s
the old aggregation/composition question again.. Putting
customised requirements into sub containers inside the CIQ published schema would
seem to be a better way forward, as a rule of thumb. From: ciq@lists.oasis-open.org
[mailto:ciq@lists.oasis-open.org] On Behalf Of Ram Kumar ---------- Forwarded message
---------- Hi Simon,
On 16 December 2011 22:00, Underhill, Simon J <Simon.Underhill@uk.bp.com>
wrote: Hello there Ram – Hope all is well. Firstly thank you for your previous note. Since then I have got
a lot closer to the CIQ specs and we hoping to use the CIQ specification as a
base for a canonical customer model within our organisation (eventually growing
this to cover all business parties). This is both a major challenge for us, as
well as a vital piece of work with a vast number of applications that use this
data with all data management issues that it involves. One question I did have with the spec is around the
relationships container in the xPIL schema. In this container there are a
number of sub-elements that hold, Name, Address, Contact numbers etc…. What I
was really looking to do was just include a reference in this container (for a
given party) to other specific Parties and then define the relationships to
them. Is this something that I am missing or is this designed in a different
way? Good question! So, what you are trying to do is define all
parties separately and use references to create relationships between parties.
What this schema does is defines a party in detail and all its relationships
with other parties (details of the parties). Hmmm.....may be use the #other
attribute to define your reference. Or, you may have to extend the schema to
include an attribute to have this reference ID.
Regards, Ram
CAUTION: This email message and any attachments contain information that may be confidential and may be LEGALLY PRIVILEGED. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is strictly prohibited. If you have received this email message in error please notify us immediately and erase all copies of the message and attachments. Thank you. ==== |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]