---
schema-version: v1.2.9
id: OASISBDX-smp-v1.0
title:
- content: Service Metadata Publishing (SMP) Version 1.0
  language:
  - en
  script:
  - Latn
  format: text/plain
  type: main
link:
- content: http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/os/bdx-smp-v1.0-os.html
  type: src
- content: http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/os/bdx-smp-v1.0-os.pdf
  type: pdf
- content: http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/os/bdx-smp-v1.0-os.doc
  type: doc
type: standard
docid:
- id: OASIS BDX-smp-v1.0
  type: OASIS
  primary: true
docnumber: BDX-smp-v1.0
date:
- type: issued
  value: '2017-08-01'
contributor:
- organization:
    name:
    - content: OASIS
    contact:
    - uri: https://www.oasis-open.org/
  role:
  - description:
    - content: Standards Development Organization
    type: authorizer
  - type: publisher
- organization:
    name:
    - content: OASIS Business Document Exchange (BDXR) TC
    contact:
    - uri: https://www.oasis-open.org/committees/bdxr/
  role:
  - description:
    - content: Committee
    type: authorizer
- person:
    name:
      given:
        forename:
        - content: Kenneth
          language:
          - en
          script:
          - Latn
      surname:
        content: Bengtsson
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Alfa1lab
        contact:
        - uri: http://www.alfa1lab.com/
    contact:
    - email: kenneth@alfa1lab.com
  role:
  - description:
    - content: Chair
    type: editor
- person:
    name:
      given:
        forename:
        - content: Jens
          language:
          - en
          script:
          - Latn
      surname:
        content: Aabol
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Difi-Agency for Public Management and eGovernment
        contact:
        - uri: http://www.difi.no/
    contact:
    - email: jea@difi.no
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Kenneth
          language:
          - en
          script:
          - Latn
      surname:
        content: Bengtsson
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Alfa1lab
        contact:
        - uri: http://www.alfa1lab.com/
    contact:
    - email: kenneth@alfa1lab.com
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Erlend
          language:
          - en
          script:
          - Latn
      surname:
        content: Klakegg
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Difi-Agency for Public Management and eGovernment
        contact:
        - uri: http://www.difi.no/
    contact:
    - email: erlend.klakegg.bergheim@difi.no
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Sander
          language:
          - en
          script:
          - Latn
      surname:
        content: Fieten
        language:
        - en
        script:
        - Latn
    contact:
    - email: sander@fieten-it.com
  role:
  - type: editor
- person:
    name:
      given:
        forename:
        - content: Sven
          language:
          - en
          script:
          - Latn
      surname:
        content: Rasmussen
        language:
        - en
        script:
        - Latn
    affiliation:
    - organization:
        name:
        - content: Danish Agency for Digitisation, Ministry of Finance
        contact:
        - uri: http://www.digst.dk/
    contact:
    - email: svrra@digst.dk
  role:
  - type: editor
language:
- en
script:
- Latn
abstract:
- content: 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. It also defines
    the request processing that must happen at the client.
  language:
  - en
  script:
  - Latn
  format: text/plain
doctype:
  type: standard
editorialgroup:
- name: OASIS Business Document Exchange (BDXR) TC
ext:
  schema-version: v1.0.1
technology_area:
- e-Business