This specification defines the representation and behaviour of DNG Configuration Management resources.
Status:
This section describes the status of this document at the time of its publication.
Other documents may supersede this document. A list of current OASIS publications can be found in the OASIS standards page at
https://www.oasis-open.org/standards.
Editor's working draft.
This document was published by the undefined as a Working Draft.
If you wish to make comments regarding this document, please send them to
@lists.oasis-open.org
(subscribe,
archives).
All comments are welcome.
Citation format:
When referencing this specification the following citation format should be used:
[DNGCM-1.0]
DOORS Next Generation Configuration Management Resources 1.0.
Edited by DNG Team.
11 December 2015.
Working Draft 01.
.
All capitalized terms in the following text have the
meanings assigned to them in the OASIS Intellectual Property Rights Policy (the
"OASIS IPR Policy"). The full Policy may be
found at the OASIS website.
This document and translations of it may be copied and
furnished to others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied, published, and
distributed, in whole or in part, without restriction of any kind, provided
that the above copyright notice and this section are included on all such
copies and derivative works. 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.
The limited permissions granted above are perpetual and will
not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is
provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that
believes it has patent claims that would necessarily be infringed by
implementations of this OASIS Committee Specification or OASIS Standard, to
notify OASIS TC Administrator and provide an indication of its willingness to
grant patent licenses to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC
Administrator if it is aware of a claim of ownership of any patent claims that
would necessarily be infringed by implementations of this specification by a
patent holder that is not willing to provide a license to such patent claims in
a manner consistent with the IPR Mode of the OASIS Technical Committee that
produced this specification. OASIS may include such claims on its website, but
disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of
any intellectual property or other rights that might be claimed to pertain to
the implementation or use of the technology described in this document or the
extent to which any license under such rights might or might not be available;
neither does it represent that it has made any effort to identify any such
rights. Information on OASIS' procedures with respect to rights in any document
or deliverable produced by an OASIS Technical Committee can be found on the
OASIS website. Copies of claims of rights made available for publication and
any assurances of licenses to be made available, or the result of an attempt
made to obtain a general license or permission for the use of such proprietary
rights by implementers or users of this OASIS Committee Specification or OASIS
Standard, can be obtained from the OASIS TC Administrator. 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. OASIS welcomes reference to, and implementation and use of,
specifications, while reserving the right to enforce its marks against
misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark
for above guidance.
Summary: The shape of a delivery session resource: all delivery session resources MUST match this shape.
DeliverySession Properties
Prefixed Name
Occurs
Read-only
Value-type
Representation
Range
Description
dcterms:title
Zero-or-one
unspecified
string
Either
Unspecified
Title (reference: Dublin Core) of the resource represented as plain text.
dng_config:policy
Zero-or-one
false
AnyResource
Inline
dng_config:DeliveryPolicy
Delivery policy.
dng_config:source
Exactly-one
true
AnyResource
Resource
oslc_config:Configuration
Source of changes to be delivered.
dng_config:target
Exactly-one
true
AnyResource
Resource
oslc_config:Configuration
Target of changes to be delivered.
oslc:serviceProvider
Zero-or-many
true
Resource
Reference
oslc:ServiceProvider
A link to the resource's OSLC Service Provider.
There may be cases when the subject resource is available from a service
provider that implements multiple domain specifications,
which could result in multiple values for this property.
Attribute which is to be treated as dominant in the source configuration of the delivery.
5. Supported Operations on Versioned Resources
A versioned resource provider MUST support the following operations on version resources:
HEAD: Retrieve information about a specific version resource.
GET: Retrieve the state of a specific version resource.
OPTIONS: Get information about the available operations on a version resource.
A versioned resource provider MAY support the following operations on version resources:
PUT: Update the state of a specific version resource;
this operation MAY succeed by creating a new version,
or MAY succeed without creating a new version
for providers that offer version resources with mutable state.
A PUT operation on a version resource MAY fail, since version resources may be immutable, or have many immutable properties.
DELETE: Delete the specified version resource.
Deletion of immutable versions, or versions used in configurations, MAY fail or MAY require specific privileges.
6. Delegated UIs
A versioned resource provider MAY provide delegated user interface dialogs for creation of new concept resources or new version resources.
A versioned resource provider SHOULD provide delegated user interface dialogs for selection of concept resources.
A versioned resource provider MAY
provide delegated user interface dialogs for selection of version
resources, but such selection is typically performed in a configuration
context to find the appropriate version.
7. Compact Rendering
A versioned resource provider SHOULD implement compact rendering, both for concept resources and version resources.
See Compact Rendering for the handling of configuration context in such rendering.
8. Tracked Resource Sets
A versioned resource provider MAY publish version resources in a Tracked Resource Set;
the URIs in the base and change log MUST be the version resource URIs, not the concept resource URIs.
All Tracked Resource Sets for version resources MUST be compliant with [TRS],
and servers providing such Tracked Resource Sets SHOULD follow the guidance in [ILDP].
