[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bdx] Groups - Inter-Cloud BDX Identity Use Cases (OASIS ID Cloud - Inter-Cloud Doc Exchange Use Case v0.11 2011-03-25.doc) uploaded
Liaisons with other TCs (e.g. ebXML) are important to promote common
profiles.
I think BDX is trying to standardize the HUB-to-HUB communication (or
SP-to-SP) in order to achieve a more wide and interoperable business
network (without borders). Today HUBs are requiring peering agreements,
but also lot of work to ensure interoperability.
The transport alone do not seems to be sufficient as we are talking about
business, registries, services.
LIME, START, ebMS are just protocols, but BDX should be something like the
common profile to route messages across different protocols and
architectures.
For instance, I could simply use FTP to send [metadata+payload] in a
meaninful way.
The way PEPPOL has leveraged Identifiers (business profiles, participants,
transactions) is the language that should travel across different networks
profiled for BDX.
Also business documents could be designed to be conformant to BDX (for
instance UBL documents could be profiled to travel a BDX-like network,
thus not requiring additional external metadata...)
I agree with Mike that it is difficult to go into any direction, but I
believe we are working on an higher level and probably we should provide a
profile for existing architectures to promote interoperability in a BDX
"fashion".
I mean BDX should describe something like a virtual backbone and also
acting as a cross-reference table to let different infrastructures will
work together.
The way PEPPOL has leveraged Identifiers (business profiles, participants,
transactions) is the language that should travel across different networks
profiled for BDX.
Also business documents could be designed to be conformant to BDX (for
instance UBL documents could be profiled to travel a BDX-like network,
thus not requiring additional external metadata...)
I a sorry if I am too cloudy... but I wanted to make some brain storming
to understand the direction taken by BDX.
Best regards,
Roberto
> Folks,
>
> Clearly, the BDX 4 corner model has a need for good use case descriptions
> and this applies to Identity and Trust as well as
> to the other aspects of the infrastructure. Equally, it is reasonable to
> ensure that the mechanisms used for the BDX specifications
> take into account the approaches adopted more widely in the industry.
>
> However, I am very concerned with what I interpret as an expansion of the
> scope of the work of the BDX TC, particularly when
> that expansion is into territory where there is already a great deal of
> activity being conducted elsewhere.
>
> "a broader framework that can encompass the various 3-corner models" is
> the first example of this expansion.
> The BDX TC is chartered to address the 4 corner model - to deal with
> 3-corner models also is to take on a lot more work
> and I think that this is inappropriate for the BDX TC.
>
> The establishment of a formal liaison between BDX and the Id-Cloud TC also
> appears to take the BDX TC into new territory.
> "Cloud Computing" is not part of the work in the charter for the BDX TC. I
> fear that an expansion of the work of the BDX TC into
> this area will be to the detriment of the work on the 4 corner model -
> Cloud computing is a big area with a lot of active work
> going on in a variety of venues. I am doubtful that venturing into this
> space will serve the BDX TC well - and that it will likely
> divert attention and energy from the matters that only the BDX TC is going
> to look at.
>
>
> In standards work, it is usually best to stay focussed, otherwise there is
> a danger of never completing anything useful.
>
>
> Yours, Mike
>
>
>
> Dr Mike Edwards
> Mail Point 137, Hursley Park
>
> STSM
> Winchester, Hants SO21 2JN
> SCA & Services Standards
> United Kingdom
> Co-Chair OASIS SCA Assembly TC
>
>
> IBM Software Group
>
>
> Phone:
> +44-1962 818014
>
>
> Mobile:
> +44-7802-467431 (274097)
>
>
> e-mail:
> mike_edwards@uk.ibm.com
>
>
>
>
>
>
>
>
> From:
> roger@traxian.com
> To:
> bdx@lists.oasis-open.org
> Date:
> 26/03/2011 18:11
> Subject:
> [bdx] Groups - Inter-Cloud BDX Identity Use Cases (OASIS ID Cloud -
> Inter-Cloud Doc Exchange Use Case v0.11 2011-03-25.doc) uploaded
>
>
>
> We had some earlier email discussion on this list about defining identity
> /
> Trust Framework use cases (a notion that Thomas Gundel I think supported).
>
> Since then, I became aware of another OASIS TC on 'Identity in the Cloud'
> (aka id-cloud). That TC has a use case analysis effort that seems well
> matched to what seemed to be needed from this TC's perspective.
>
> This initial draft is in considerable need of improvement, not least as to
> my various errors and mis-characterizations of the BDX Addressing/Security
> models. As stated in the document, one goal was to define a broader
> framework that can encompass the various 3-corner network models, and
> facilitate easy, end-to-end connection setup more broadly.
>
> Feedback and suggested edits are very welcome. If the TC agrees, we might
> even collaborate to get this to 'Approved Document' status for
> re-submission to the Id-Cloud TC. (I have already posted it there for
> feedback from that group).
>
> I would also like to propose establishing a formal liaison relationship
> between the two TCs. Id-Cloud TC members also seem well plugged into the
> world of identity standards (i.e. KI, OIX etc) and may have useful input
> about how best to move this forward.
>
> The goal, obviously, is to get broad buy-in and adoption, in particular by
> some of the larger industry players. With that in mind, the document uses
> the term 'Inter-Cloud' to position the BDX requirements as a leading edge
> use case for a big, important shift in the Cloud Computing world more
> generally.
>
> I look forward to any feedback and further discussion, whether via
> document
> comments here, on the email list, or on upcoming TC calls.
>
> Best regards,
> Roger Bass
>
>
>
>
> -- Roger Bass
>
> The document named Inter-Cloud BDX Identity Use Cases (OASIS ID Cloud -
> Inter-Cloud Doc Exchange Use Case v0.11 2011-03-25.doc) has been submitted
> by Roger Bass to the OASIS Business Document Exchange TC document
> repository.
>
> Document Description:
> Use cases relating to identity issues in "Inter-Cloud" business
> document exchange, including both 4-corner and 3-corner scenarios.
>
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=41623
>
> Download Document:
> http://www.oasis-open.org/committees/download.php/41623/OASIS%20ID%20Cloud%20-%20Inter-Cloud%20Doc%20Exchange%20Use%20Case%20v0.11%202011-03-25.doc
>
>
>
> PLEASE NOTE: If the above links do not work for you, your email
> application
> may be breaking the link into two pieces. You may be able to copy and
> paste
> the entire link address into the address field of your web browser.
>
> -OASIS Open Administration
>
>
>
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
>
>
>
>
--
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor
Roberto Cisternino
mobile: +39 328 2148123
skype: roberto.cisternino.ubl-itlsc
[UBL Technical Committee]
http://www.oasis-open.org/committees/ubl
[UBL Online Community]
http://ubl.xml.org
[UBL International Conferences]
http://www.ublconference.org
[UBL Italian Localization Subcommittee]
http://www.oasis-open.org/committees/ubl-itlsc
[Iniziativa divulgativa UBL Italia]
http://www.ubl-italia.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]