[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-msg] Restructuring
Pulling is based on MPCs, not on particular party identifiers. To prevent one business from accidentally pulling a message for some other partner, the messages should be assigned to different MPCs, with each party only authorized for its own channel. The part 2 spec, section 2.5.4 has a concept called sub-channels that is intended to make this a bit more flexible, but it is not part of AS4. Pim -----Original Message----- From: Theo Kramer [mailto:theo@flame.co.za] Sent: 01 July 2011 10:51 To: Pim van der Eijk Cc: ebxml-msg@lists.oasis-open.org Subject: Re: [ebxml-msg] Restructuring We have identified a problem with pull on AS4 which I believe needs discussion. I planned drafting an email on that after the webinar. Not sure if that should hold up the restructuring exercise but I do think that it wise to resolve this prior to final upload of AS4. The main problem is identifying the partners and p-modes for a pull request. This due to the authorization/authentication not explicit within the signal itself. It is possible to determine these from non-normative third party libraries for usernameTokens in WSL or SSL but do not think that is the way to go. On 01 Jul 2011, at 9:26 AM, Pim van der Eijk wrote: > Hello, > > TC Admin suggests a possible restructuring of the "profiles" directory on the docs.oasis-open.org site and as they are getting ready to finally upload AS4, now might be a good time to make this change. Any opinions? > > Pim > > Quoting from the email: > > We could even exit the /200707/ directory and start putting all new > "profiles" releases under /profiles/ rather than under /200707/ > > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/ > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4/ > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/conf ormance/ > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/prof ileFoo/ > > OR, just: > > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/2007 07/AS4/csd > 04 > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/2007 07/AS4/csd > 05 > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/2007 07/AS4/csp > rd0x > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/2007 07/AS4/cs0 > 1 > http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/2007 07/AS4/os > > Of course, we need to honor the "Latest Version:" URIs for all Work Products so that documents published to date always resolve to "latest", no matter what the location. I can do that with URI rewrites and symlinks. The namespace name (http://docs.oasis-open.org/ebxml-msg/ns/ebms/v3.0/profiles/ 200707 ) will be unaffected because we use URI rewrites, and it does not matter where the namespace document lives. > Pim -- Regards Theo
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]