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


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

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

Subject: RE: [oasis-charter-discuss] Proposed Charter for OASIS BusinessDocument Exchange (BusDox) TC

Under Statement of Purpose it says "The purpose of the BusDox TC is to define, enhance and maintain profiles of existing standards (from OASIS and elsewhere)". I assume this implies an ordering - define first, then enhance/maintain, as opposed to maintain a profile defined  outside of OASIS? Please clarify.

I would like the charter to be a more specific on its deliverables.
In the List of Deliverables section it just talks about a set of Committee Specifications, but does not list them. It only enumerates what the contents of the deliverables might look like, an expected list of committee specifications. I understand that a TC will be able to change its mind, but a list of anticipated deliverables is always nice to know. 

Furthermore, the sentence "The first two drafts of the Committee Specifications will be based on the specifications made by the PEPPOL project (see http://www.peppol.eu/work_in_progress/wp8-Solutions%20architecture%2C%20design%20and%20validation/results/d8.2-version-1.0-of-the-peppol-infrastructure/d8.2-version-1.0-of-the-peppol-infrastructure)." is confusing in two regards 1) what is meant by "the first two drafts"? Normally a TC will accept a contribution and then work within OASIS to produce subsequent drafts 2) the link points to a single specification, so to me this needs tidying up wrt to my point above.

> -----Original Message-----
> From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
> Sent: 27 October 2010 07:19
> To: members@lists.oasis-open.org; tc-announce@lists.oasis-open.org
> Cc: oasis-charter-discuss@lists.oasis-open.org; Jens Jakob Andersen; Mikkel
> Hippe Brun; Pim van der Eijk; Tim McGrath; andrea.caccia@studiocaccia.com;
> tg@itcrew.dk; Paul Fremantle; gianfranco.tabasso@fmsgroup.it
> Subject: [oasis-charter-discuss] Proposed Charter for OASIS Business
> Document Exchange (BusDox) TC
> To OASIS Members:
>   A draft TC charter has been submitted to establish the OASIS Business
> Document Exchange (BusDox)  Technical Committee (below). In accordance with
> the OASIS TC Process Policy section 2.2:
> (http://www.oasis-open.org/committees/process-2010-07-28.php#formation) the
> proposed charter is hereby submitted for comment. The comment period shall
> remain open until 11:45 pm ET on 10 November 2010.
>   OASIS maintains a mailing list for the purpose of submitting comments on
> proposed charters. Any OASIS member may post to this list by sending email
> to:
> mailto:oasis-charter-discuss@lists.oasis-open.org. All messages will be
> publicly archived at:
> http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who
> wish to receive emails must join the group by selecting "join group" on the
> group home page:
> http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/.
> Employees of organizational members do not require primary representative
> approval to subscribe to the oasis-charter-discuss e-mail.
>   A telephone conference will be held among the Convener, the OASIS TC
> Administrator, and those proposers who wish to attend within four days of
> the close of the comment period. The announcement and call-in information
> will be noted on the OASIS Charter Discuss Group Calendar.
>   We encourage member comment and ask that you note the name of the proposed
> TC (BusDox) in the subject line of your email message.
> Regards,
> Mary
> Mary P McRae
> Director, Standards Development
> Technical Committee Administrator
> Member Section Administrator
> OASIS: Advancing open standards for the information society
> email: mary.mcrae@oasis-open.org
> phone: 1.603.232.9090
> Standards are like parachutes: they work best when they're open.
> Important Links for all TC Members:
> TC Handbook: http://docs.oasis-open.org/TChandbook/
> TC Process: http://www.oasis-open.org/committees/process-2010-07-28.php
> -----
> OASIS Business Document Exchange (BusDox) Technical Committee
> Name of the TC:
> OASIS Business Document Exchange (BusDox) Technical Committee
> Statement of Purpose:
> The purpose of the BusDox TC is to define, enhance and maintain profiles of
> existing standards (from OASIS and elsewhere) that specify interfaces for a
> lightweight and federated messaging infrastructure supporting a 4-corner
> model(1) of secure and reliable exchange of electronic documents.
> The BusDox TC does not replace existing messaging service standards. It
> provides a simplified interface independent of the various standards used
> for the exchange of documents.
> The foundation for the work are the specifications developed as part of the
> PEPPOL(2) project, providing the infrastructure for public eProcurement in
> Europe. But the specifications can be used for any business processes. It is
> intended that the OASIS BusDox TC will become the maintenance forum for
> interfaces implemented by the PEPPOL project and similar infrastructure
> initiatives.
> Scope of work of the TC:
> The objectives will be to:
> 1.    Establish profiles for a lightweight and federated document transport
> infrastructure supporting secure and reliable exchange of electronic
> business documents.
> 2.    Profile and maintain a robust, secure and lightweight addressing
> mechanism capable of exposing metadata about endpoints (including supported
> business processes, content standards and transport protocols, security
> requirements) and able to be operated in a highly distributed environment.
> 3.    The addressing mechanism must support dynamic creation of connections
> based on look-up of services at runtime.
> 4.    Profile and maintain suitable secure, trusted, asynchronous and
> reliable messaging protocols such as START, ebMS and AMQP.
> 5.    Profile and maintain the Lightweight Message Exchange (LIME), a secure
> and reliable lightweight messaging protocol.
> 6.    Define a profile of the WS-* based ebMS 3.0 Core standard and its
> newer AS4 profile and multi-hop feature, that provide end-to-end security
> and reliability.
> 7.    Support an open infrastructure capable of implementing a 4-corner
> model of network interconnections.
> 8.    Develop specifications that support service levels appropriate for
> large scale deployment.
> Out of scope
> The BusDox TC will not profile synchronous end-to-end messaging protocols,
> as they are not appropriate in a 4-corner model of network interconnections.
> However the addressing mechanism should be equally suitable for synchronous
> and asynchronous exchanges and can therefore be used in synchronous
> scenarios not covered by the 4-corner model.
> List of deliverables
> The BusDox TC will produce an integrated set of Committee Specifications
> including a set of XML Schemas and an XML-based request/response protocol
> for exchange of documents.
> Committee Specifications will cover:
> 1.    Profiles for a robust, secure, federated and lightweight addressing
> mechanism.
> 2.    Profiles for one or more secure, trusted, asynchronous and reliable
> messaging protocols. The initial profile to be covered will be the START
> profile (Secure Trusted Asynchronous Reliable Transport).
> 3.    A profile of a secure and reliable, lightweight messaging protocol,
> LIME (Lightweight Message Exchange).
> 4.    A profile of ebMS 3.0, its multi-hop feature and AS4 profile.
> 5.    Test and conformance suites aiding the development of interoperable
> implementations of the profiles.
> The first two drafts of the Committee Specifications will be based on the
> specifications made by the PEPPOL project (see
> http://www.peppol.eu/work_in_progress/wp8-
> Solutions%20architecture%2C%20design%20and%20validation/results/d8.2-
> version-1.0-of-the-peppol-infrastructure/d8.2-version-1.0-of-the-peppol-
> infrastructure).
> This will be the main focus of the first 9 months.
> The BusDox TC intends that the Committee Specifications will become OASIS
> standards.
> It is estimated that the delivery of an initial set of specifications will
> take one to two years.
> It is the goal that the first deliverables will be as follows:
> .    March 2011: BusDox TC Draft specifications under OASIS namespaces based
> on PEPPOL specifications.
> .    July 2011: BusDox TC Committee specifications for implementation by the
> PEPPOL project.
> .    October 2011: Public review of OASIS BusDox specifications
> .    December 2011: BusDox TC Committee specifications.
> .    January 2012: BusDox 1.0 becomes an OASIS standard
> IPR Mode under which the TC will operate
> The TC will operate under the Non-Assertion Mode.
> The anticipated audience or users of the work
>  The initial target groups for the BusDox TC are:
> 1.    Service providers and self service providers (for example Value Added
> Network Operators, Banks, eProcurement solution providers etc).
> 2.    Software companies (e.g. suppliers of middleware and software
> platforms)
> 3.    Public institutions
> 4.    Large private companies
> Language of the Technical Committee
> The business of the Technical Committee will be conducted in English.
> Non-normative information regarding the startup of the TC:
> Similar or applicable work
> A number of OASIS TC's and groups belonging to other standards organizations
> have covered and are covering similar subject areas as the BusDox TC.
> .    OASIS UDDI Specification TC (finished): The purpose of the Universal
> Description, Discovery, and Integration (UDDI) Specification TC is to
> continue work on the Web services registry foundations developed and
> published
> byUDDI.org
> . The UDDI specifications form the necessary technical foundation for
> publication and discovery of Web services implementations both within and
> between enterprises.
> .    OASIS ebXML Messaging Services Technical Committee: The purpose of this
> TC is to develop and recommend technology for the transport, routing and
> packaging of business transactions using standard Internet technologies.
> This work will foster consistency across specifications developed in other
> forums and carry forward the work started in the ebXML Transport, Routing
> and Packaging project team
> .    OASIS ebXML Registry TC: The OASIS ebXML Registry TC develops
> specifications to achieve interoperable registries and repositories, with an
> interface that enables submission, query and retrieval on the contents of
> the registry and repository. Further, the Registry TC seeks to develop
> specifications that serve a wide range of uses, covering the spectrum from
> general purpose document registries to real-time business-to-business
> registries. Additionally, as part of its specification development work,
> this TC explores and promotes various emerging models for distributed and
> cooperating registries.
> .    WS-I Basic Security Profile Working Group: is developing an
> interoperability profile dealing with transport security, SOAP messaging
> security and other Basic-Profile-oriented Web services security
> considerations. The Working Group is developing and selecting a set of usage
> scenarios and their component message exchange patterns to guide the
> profiling work.
> .    IETF Network Working Group: MIME-Based Secure Peer-to-Peer Business
> Data Interchange Using HTTP, Applicability Statement 2 (AS2). AS2 describes
> how to exchange structured business data securely using the HTTP transfer
> protocol, instead of SMTP; the applicability statement for SMTP is found in
> RFC 3335.  Structured business data may be XML; Electronic Data Interchange
> (EDI) in either the American National Standards Committee (ANSI) X12 format
> or the UN Electronic Data Interchange for Administration, Commerce, and
> Transport (UN/EDIFACT) format; or other structured data formats.  The data
> is packaged using standard MIME structures.  Authentication and data
> confidentiality are obtained by using Cryptographic Message Syntax with
> S/MIME security body parts.  Authenticated acknowledgements make use of
> multipart/signed Message Disposition Notification (MDN) responses to the
> original HTTP message.
> .    AMQP Working Group: The AMQP Working Group collaborate on
> specifications for messaging infrastructure that provides an facility for
> connecting messaging-dependent applications. AMQP's scope covers messaging
> within and between firms, with applicability to both business and
> infrastructure messaging.
> The work of the BusDox TC does compete with the work of various groups
> mentioned above. A BusDox compliant infrastructure may be realized using
> software implementing one of these specifications.
> First meeting
> The first meeting will be held on December 17 2010 (at 14:00 CET) as a two
> hour conference call. The meeting facility will be available at
> https://connect.forskningsnettet.dk/peppolwp8. Sign in as guest.
> Meeting schedule
> The TC will hold one weekly conference call and in addition to face-2-face
> meetings twice a year (November and May). Face-2-face meetings will be
> sponsored by the members of the TC.
> The names, electronic mail addresses, and membership affiliations of at
> least Minimum Membership who support this proposal:
> Jens Jakob Andersen, jjan@itst.dk, Denmark Ministry of Science, Technology &
> Innovation
> Mikkel Hippe Brun, mhb@tradeshift.com, Tradeshift Network Ltd.
> Pim van der Eijk, pvde@sonnenglanz.net, Sonnenglanz
> Tim McGrath, tim.mcgrath@documentengineeringservices.com, Document
> Engineering Services
> Andrea Caccia, andrea.caccia@studiocaccia.com, AITI - Associazione Italiana
> dei Tesorieri d'Impresa
> Thomas Gundel, tg@itcrew.dk, Individual Member
> Paul Fremantle, paul@wso2.com, WSO2
> Primary Representative statements of support:
> Denmark Ministry of Science, Technology & Innovation
> "The Danish National IT and Tele Agency (NITA) fully supports the idea of
> creating this TC within the framework of OASIS.
> Denmark has developed and implemented both technical solutions, as well as
> legislation in this area, to create an effective and dynamic National
> ecommerce infrastructure, that generates substantial savings for both
> private and public sector.
> We see a standardization within OASIS as the natural next step, to ensure
> that the knowhow is forwarded to the global community."
> Jens Jakob Anderesen, jjan@itst.dk, Denmark Ministry of Science, Technology
> & Innovation
> Tradeshift Network Ltd
> "Tradeshift Network Ltd fully supports and intends to participate in the
> OASIS BusDox TC. Lowering barriers for SME's use of messaging
> infrastructures is of key importance in the coming years - especially in the
> fields of e-invoicing and supply chain connectivity. We believe that the
> BusDox TC will be an important enabler in this quest."
> Mikkel Hippe Brun, mhb@tradeshift.com, Tradeshift Network Ltd.
> Sonnenglanz Consulting
> "As the primary representative of Sonnenglanz Consulting to OASIS, I
> officially inform you of our company's intention to participate in the OASIS
> BusDox TC."
> Pim Van der Eijk , pvde@sonnenglanz.net, Sonnenglanz Consulting
> Document Engineering Services
> "Document Engineering Services supports and intends to participate in the
> OASIS BusDox TC."
> Tim McGrath, tim.mcgrath@documentengineeringservices.com, Document
> Engineering Services
> "I confirm that AITI - Associazione Italiana dei Tesorieri d'Impresa, Oasis
> member, is interested to participate to this new TC."
> Gianfranco Tabasso,  AITI - Associazione Italiana dei Tesorieri d'Impresa
> (gianfranco.tabasso@fmsgroup.it)
> WSO2
> "I, Paul Fremantle, as the Primary Representative to OASIS for WSO2, provide
> support to create the BUSDOX TC at OASIS"
> Paul Fremantle, paul@wso2.com, WSO2
> Convenor
> The Convenor will be Mikkel Hippe Brun (mhb@tradeshift.com).
> The name of the Member Section with which the TC intends to affiliate, if
> any
> N/A or name of member section
> A list of contributions of existing technical work that the proposers
> anticipate will be made to this TC
> N/A
> Optionally, a draft Frequently Asked Questions (FAQ) document
> N/A
> Optionally, a proposed working title and acronym for the specification(s) to
> be developed by the TC
> N/A
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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