[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] FW: Namespace management
Joe, I do not believe so - since you can reference the pieces exactly as you need: <registry alias="UBL-01" "http://ubl-ref.org/port:1001"/> <registry alias="UBL-02" "http://ubl-walmart-ref.org/port:2001"/> And then you'd reference the content accordingly. Notice these references are in the external CAM template, NOT the XML markup itself. So you have ultimate flexiblity. If you say merge those Walmart extensions into the main library - now all you have to do is change the one line in the template - the address URL of the alias reference. I beleive this reinforces my earlier statement - that keeping the XML transaction completely clean and simple - and putting the metadata associations into the script mechanism is the way forward. You can supplement that with localized checking via schema for simple things like datatypes, repeat counts, et al, but trying to make your schema your ebusiness integration system is not what schema was ever designed for. Thanks, DW. ============================================================= Message text written by Chiusano Joseph > Which ties a construct to a specific registry (which is valuable in many cases). But what about cases where the constructs that comprise a vocabulary with an assigned namespace identifier are stored in multiple registries? Doesn't this defeat the whole purpose of federation? This seems more restrictive to me than namespaces might even now be seen. < ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]