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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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


Subject: guidelines on usage of namespaces


Dear all,

Over the last couple of weeks, we've had internally some interesting discussions on the use of namespaces.
One of the purposes of Namespaces is to avoid data element collision. Now my question is: how granular can one apply a namespace. Is
it the purpose to have different namespaces at the level of the industry (e.g. Automotive vs financial), at the level of the
business (e.g. securities vs. payments), technical vs. business (e.g. envelope info vs. payload), at an even lower level (per
business scenario), or even lower?
What are the consequences of having many namespaces?
Has anyone encountered alike discussions?
Should we need to provide some recommendations on when to use namespaces vs. renaming elements (or other methods such use of as
Xlink and Xpointer) to solve collisions?
Should this be discussed in this group or in another (e.g. Core Components, or Repository)?


Best Regards
Kris
begin:vcard 
n:Ketels;Kris
tel;fax:+32.2.655.45.52
tel;work:+32.2.655.44.85
x-mozilla-html:FALSE
org:S.W.I.F.T. sc;Standards
adr:;;;;;;
version:2.1
email;internet:kris.ketels@swift.com
title:Product Manager Standards
x-mozilla-cpt:;1
fn:Kris Ketels
end:vcard


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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC