[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Form submission from: Request a Special Majority Vote to proceed to Candidate OASIS Standard
Submitted on Thursday, March 2, 2017 - 12:26 Submitted by user: Submitted values are: Your name: Kenneth Bengtsson TC name: OASIS Business Document Exchange (BDXR) TC TC email address: bdxr@lists.oasis-open.org Title: Service Metadata Publishing (SMP) Version 1.0 Committee Specification 03 Committee Specification URI: http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/cs03/ Committee Specification editable source URI(s): http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/cs03/bdx-smp-v1.0-cs03.doc Certification by the TC that all schema and XML instances are well-formed and that expressions are valid: We so certify Clear English-language summary of the specification: Service Metadata Publishing (SMP) describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient (endpoint) of the business document, such as types of documents the endpoint is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. SMP also defines the request processing that must happen at the client. Relationship of this specification to similar work: The Service Metadata Publishing (SMP) specification is related to the Business Document Metadata Service Location (BDXL) specification, also developed by the BDXR TC. Together they form a complete mechanism for entities to discover how to successfully exchange business document in a 4-corner network, such as ascertaining endpoint addresses, transport protocols and document formats. --Statements of Use-- Link to Statement of Use #1: https://lists.oasis-open.org/archives/bdxr-comment/201609/msg00001.html Link to Statement of Use #2: https://lists.oasis-open.org/archives/bdxr/201611/msg00003.html Link to Statement of Use #3: https://lists.oasis-open.org/archives/bdxr-comment/201611/msg00000.html Additional Statements of Use: https://lists.oasis-open.org/archives/bdxr/201609/msg00008.html https://lists.oasis-open.org/archives/bdxr/201610/msg00007.html --Public Reviews-- First public review announcement URI: https://lists.oasis-open.org/archives/tc-announce/201605/msg00000.html Comment resolution log: https://lists.oasis-open.org/archives/bdxr/201606/msg00017.html Additional public review announcement URIs: Additional comment resolution log URIs: http:// Approval link: https://lists.oasis-open.org/archives/bdxr/201612/msg00006.html Earlier attempts to standardize: No Sources of explanatory information: Notes: SMP and BDXL are in common use in 4-cornered public networks around the world, such as in Australia where they are used in the public-private e-invoicing infrastructure (see http://digitalbusinesscouncil.com.au/digital-capability-locator/ and http://digitalbusinesscouncil.com.au/digital-capability-publisher/), and in the European Union where they are used by the Commission and its Member States for cross-border exchange of business documents such as in public procurement, healthcare and for legal documents between courts (see http://ec.europa.eu/inea/sites/inea/files/building_block_dsi-introdocument_edelivery_v1_00.pdf). The results of this submission may be viewed at: http://tools.oasis-open.org/issues/browse/TCADMIN
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]