XML Namespace Document for Field Force Management Integration Interface Specification Version 1.0

05 October 2012

Introduction

This document describes the XML namespace names declared in the specification Field Force Management Integration Interface Specification Version 1.0, CS01:

• http://docs.oasis-open.org/ffm/ns/v1.0/ws/implementation
• http://docs.oasis-open.org/ffm/ns/v1.0/ws/manager
• http://docs.oasis-open.org/ffm/ns/v1.0/common/api
• http://docs.oasis-open.org/ffm/ns/v1.0/common/model
• http://docs.oasis-open.org/ffm/ns/v1.0/system/info/api
• http://docs.oasis-open.org/ffm/ns/v1.0/system/info/model
• http://docs.oasis-open.org/ffm/ns/v1.0/system/capability/api
• http://docs.oasis-open.org/ffm/ns/v1.0/system/capability/model
• http://docs.oasis-open.org/ffm/ns/v1.0/wrm/api
• http://docs.oasis-open.org/ffm/ns/v1.0/wrm/model
• http://docs.oasis-open.org/ffm/ns/v1.0/firm/api
• http://docs.oasis-open.org/ffm/ns/v1.0/firm/model
• http://docs.oasis-open.org/ffm/ns/v1.0/rdm/api
• http://docs.oasis-open.org/ffm/ns/v1.0/rdm/model
• http://docs.oasis-open.org/ffm/ns/v1.0/rdm/model/profile

Namespace URI Versioning Policy

It is the intent of the OASIS Field Force Management (FFM) TC that XML namespace names identified by URI references will not change arbitrarily with each subsequent revision of the corresponding WSDL or XML Schema documents but rather change only when a subsequent revision, published in conjunction with a Committee Specification Draft, results in non-backwardly compatible changes from a previously published Committee Specification Draft.

Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a new namespace URI:

• addition of new global element, attribute, complexType and simpleType definitions
• addition of new operations within a WSDL portType or binding (along with the corresponding schema, message and part definitions)
• addition of new elements or attributes in locations covered by a previously specified wildcard
• modifications to the pattern facet of a type definition for which the value-space of the previous definition remains valid or for which the value-space of the preponderance of instance would remain valid
• modifications to the cardinality of elements for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule

Related Resources for the FFM Integration Interface Version 1.0 XML Namespace Names

Normative Reference:

XML Schemas and WSDL: