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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

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

Subject: [ubl-ndrsc] RE: Question: qualified element names in top-level messagedefs

Hello Dave,

the problem is, there are top level BIEs defined in the spreadsheets of every business document 'Invoice', 'Order' etc. If the declared elements will be not fully qualified, they would be going into conflict with the reusable types. I can solve this problem, if I define for the reusable types a
namespace. All element names of the reusable types will get a prefix (e.g. 'bie') in every document structure. But we will se this prefix in every xml instance.

Kind regards,


-----Original Message-----
From: Dave Carlson [mailto:dcarlson@ontogenics.com] 
Sent: Mittwoch, 22. Januar 2003 20:32
To: ubl-ndrsc@lists.oasis-open.org; Stuhec, Gunther
Cc: jon.bosak@sun.com
Subject: Question: qualified element names in top-level message defs

It seems strange, and a bit inconsistent, to have element names fully qualifed
with object class term in top-level defintions, but not in the reusable types.

See the attached UML diagram (which is pruned to show less detail for this

Why are all child element names of DespatchAdvice prefixed with

e.g. we have "DespatchAdviceIssueDate"
but in ReferencedOrder, we have simply "IssueDate"

This this the intended rule?

(Again, could someone copy this message to ubl-lcsc ?)

-- Dave

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

Powered by eList eXpress LLC