Lists Home |
Date Index |
The problem is:
there are a, b, c and d entities that can be represented with the same type
there is e entity that can be represented with type y which is derivation
of type x.
there is need to identify a, b, c, d and distinguish between them
all these entities are used in the same transaction where any combination
of entities is allowed
1.use elements a type x, b type x, c type x, d type x and e type y; place
them in the transaction as optional elements; the solution is clean but
requires rigid order of elements in the transaction.
2.create types for each entity: type ax, type bx, type cx .... ; use
xsi:type in the transaction; result flexible structure, allows any order of
entities but requires multiple definition of the same type.
3. use the same type x for a,b,c and d and use the xsi:type in the
transaction and use an additional element in the type x to distinguish
between a, b, c and d. The solution is flexible, but as y inherits from x,
the same additional element will appear in y. y type uniquely identifies
entity e and this additional element is not required. By being there it
provides two sources of information for the identification of entity e.
This may confuse the application, not mentioning possibility that the two
information may be inconsistent.
Please advice the preference of the above options or .... even better ...
suggest more appropriate options.
This e-mail is confidential. If you are not the intended recipient, any use, disclosure or copying of this document is unauthorised and prohibited. If you have received this document in error, please delete the email and notify me by return email or by phoning the NEMMCO Helpdesk on 1300 300 295.