Interopera dating the undertaker dating
OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs.
This version: version: version: Committee: Ryan Mc Veigh ([email protected]), Zia Consulting Florian Mller ([email protected]), Alfresco Additional artifacts: This prose specification is one component of a Work Product which also includes: XML examples: Related work: This specification is related to: Content Management Interoperability Services (CMIS) Version 1.0. XML namespaces: Abstract: The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services and Restful Atom Pub bindings that can be used by applications to work with one or more Content Management repositories/systems.
The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces.
Additional object-types MAY be defined in a repository as subtypes of these base types.
CMIS services are provided for the discovery of object-types that are defined in a repository.
Status: This document was last revised or approved by the OASIS Content Management Interoperability Services (CMIS) TC on the above date. Check the Latest version location noted above for possible later revisions of this document. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
However, object-type management services, such as the creation, modification, and deletion of an object-type, are outside the scope of CMIS.
Every CMIS object has an opaque and immutable Object Identity (ID), which is assigned by the repository when the object is created.
Every CMIS object has a set of named, but not explicitly ordered, Properties.
(However, a Repository SHOULD always return object properties in a consistent order.) Within an object, each property is uniquely identified by its property definition id.