OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Extend scope of C001 Assigning_identifiers?


Title: Extend scope of C001 Assigning_identifiers?

All.

Based on findings in the Synchronization workshops, it is recommended that the powerful capabilities in DEXLib are tailored to specific business constraints by specializations, and that the specialized capability is instantiated for the specific business data to be exchanged.

Furthermore, it is recommended that a specific DEX is populated by instantiated capabilities. The specific DEX shall be defined as an instantiation of the more generic DEX at the level currently defined in DEXLib. Specialized capabilities, instantiated capabilities and instantiated DEXes are all subject to standardization.

Following the above scenario, Capability C001 Assigning_identifiers meets requirements for a specialized capability (subset of a larger capability, but not detailed enough for an instance of a capability). A larger capability should allow that the identifier owner (C016 Representing_person_organization) may or may not be assigned to an Identification_assignment. Similarly with C036 Assigning_date_time.

Currently, C001 seems to require that the ID owner shall be assigned, however there is no such formal statement. This would also not be possible with the existing Express listing as it does not include C016 nor C036. 

Hence, rules that combine information elements from e.g. C001, C016 and C036 need to be stated in each instance of a DEX that has such a requirement. We should try to avoid that different DEXes hold identical rules combining C001, C016 and C036.

A solution could be to extend the scope of C001 to import C016 and C036 (formalization of Fig 2 arrangement in C001). Specializations for C001 could then be made to formalize alternative sub arrangements.

Until this issue is resolved, the template proposal DEX000 (which when developed into a real DEX should be an instance of DEX001) will be provided with a rule to mandate usage of C016 in the context of C001."


 Regards
Trine Hansen
UCTNO940, Information Quality Management
Det Norske Veritas AS
( + 47 67 57 96 38 (office)
( + 47 90 83 44 24 (mobile)
* trine.hansen@dnv.com
http://www.dnv.com



**************************************************************
Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet. All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of malicious code. DNV acknowledges that unsolicited email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted. DNV has disabled "out of office" replies to Internet transmitted e-mail.
**************************************************************


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]