OSLC Architecture Management Version 2.1. Part 1: Specification

This specification defines the OSLC Architecture Management domain, a RESTful web services interface for the management of architectural resources and relationships between those and related resources such as product change requests, activities, tasks, requirements or test cases. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, as well as HTTP response codes, content type handling and resource formats.

Status:

This document was last revised or approved by the OASIS OSLC Lifecycle Integration Domains TC on the above date. The level of approval is also listed above. Check the “Latest version” location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oslc-domains#technical.

TC members should send comments on this specification to the TC’s email list. Others should send comments to the TC’s public comment list oslc-domains-comment@lists.oasis-open.org, after subscribing to it by following the instructions at the “Send A Comment” button on the TC’s web page at https://www.oasis-open.org/committees/oslc-domains/.

This specification is provided under the RF on Limited Terms Mode of the OASIS IPR Policy, the mode chosen when the Technical Committee was established. For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the TC’s web page (https://www.oasis-open.org/committees/oslc-domains/ipr.php).

Note that any machine-readable content (Computer Language Definitions) declared Normative for this Work Product is provided in separate plain text files. In the event of a discrepancy between any such plain text file and display content in the Work Product's prose narrative document(s), the content in the separate plain text file prevails.

Citation format:

When referencing this specification the following citation format should be used:

[OSLC-AM-2.1-Part1]
OSLC Architecture Management Version 2.1. Part 1: Specification. Edited by Jim Amsden. 16 August 2018. OASIS Committee Specification Draft 01 / Public Review Draft 01. http://docs.oasis-open.org/oslc-domains/oslc-am/v2.1/csprd01/part1-architecture-management-spec/oslc-am-v2.1-csprd01-part1-architecture-management-spec.html. Latest version: http://docs.oasis-open.org/oslc-domains/oslc-am/v2.1/oslc-am-v2.1-part1-architecture-management-spec.html.

Notices

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 https://www.oasis-open.org/policies-guidelines/trademark for above guidance.

1. Introduction

This section is non-normative.

This specification defines a RESTful web services interface for the Architecture Management (AM) domain. This domain addresses the management of product design artifacts including models, and relationships with other resources such as requirements, testing resources and change requests. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, content type handling and resource formats..

The intent of this specification is to define the capabilities needed to support integration scenarios defined by the Architecture Management working group and not to provide a comprehensive interface to Architecture Management. The resource formats and operations may not match exactly the native artifacts supported by architecture management AM Servers but are intended to be compatible with them. The approach to supporting these scenarios is to delegate operations, as driven by service provider contributed user interfaces, as much as possible and not require a service provider to expose its complete data model and application logic.

This specification is a [OSLCCore3] compliant specification, and as such most of its content are references to [OSLCCore3].

1.1 IPR Policy

1.2 Terminology

Resource: An artifact used in the Application Lifecycle Management (ALM) space. A resource is directly addressable with an absolute URL.
Architecture Management Resource (AMR): Directly addressable resources of some domain/notation (i.e. UML, BMPN, ER) that represent an abstraction of some behavior or construct of a system under development. An AMR maintains its identity after refactoring. In the semantic web, an AMR might correspond to a graph that is an instance of some vocabulary or micro-theory.
Link: A logical relationship from one resource to another resource. An OSLC AM Link is uni-directional. The subject (source) of a link represents the resource that "knows about" and is referencing another resource (target). The type of relationship is given by a predicate URI (link type). In semantic web terminology, a link would correspond to an RDF statement with a subject (source), a predicate (type) and object (target). The predicate could be defined by property in an RDF schema.
Link type (LT): A URI that represents the type of a link. In semantic web terminology it is the predicate of an RDF triple. It clarifies the type of relationship between two resources. Link Type URIs may be defined locally, within the OSLC, or externally (i.e. Dublin Core terms). Link types could be defined in RDF Schemas.
Link type Resource (LTR): A resource that contains human consumable information about a Link Type, like its human readable name and description. The resource is managed by the AM provider. The information may be about a Link Type in a different domain (i.e. Dublin Core Terms or OWL). The main use of an LTR is for clients who want to build a UI for users that clearly labels potential link types.
AM Client: An implementation of the OSLC Architecture Management specifications as a client. OSLC AM Clients consume services provided by AM servers.
AM Server: A server implementing the OSLC Architecture Management domain specifications. OSLC AM clients consume services provided by AM Servers. The use of the terms Client and Server are intended to distinguish typical consumers and providers of OSLC resources in a distributed environment based on REST. A particular application component could be a client for some OSLC domain services and a server for the same or another domain.

1.3 References

1.3.1 Normative references

[OSLCCore2]: Dave Johnson; S. Speicher. OSLC Core Specification 2.0. Finalized. URL: http://open-services.net/bin/view/Main/OslcCoreSpecification
[OSLCCore3]: Jim Amsden; S. Speicher. OSLC Core 3.0. Committee Specification. URL: http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part1-overview.html
[OSLCPreview]: OSLC Resource Preview 3.0. Committee Specification. URL: http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part3-resource-preview.html
[OSLCShapes]: Arthur Ryman; Jim Amsden. OSLC Resource Shape 3.0. URL: http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part6-resource-shape.html
[RFC2119]: S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119

1.3.2 Informative references

[LDPPatch]: Linked Data Patch Format. Working Group Note. URL: http://www.w3.org/TR/ldpatch/

1.4 Typographical Conventions and Use of RFC Terms

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this specification are to be interpreted as described in [RFC2119].

2. Base Requirements

The following sub-sections define the mandatory and optional requirements for an OSLC Architecture Management (OSLC AM) server.

2.1 Base Compliance

This specification is based on [OSLCCore3]. OSLC AM servers MUST be compliant with both the core specification, MUST follow all the mandatory requirements in the normative sections of this specification, and SHOULD follow all the guidelines and recommendations in both these specifications. [AM-1]

An OSLC AM server MUST implement the domain vocabulary defined in OSLC Architecture Management Version 2.1. Part 2: Vocabulary [AM-2]

The following table summarizes the requirements from OSLC Core Specification as well as some additional requirements specific to the AM domain. Note that this specification further restricts some of the requirements from the OSLC Core Specification. See the previous sections in this specification or the OSLC Core Specification to get further details on each of these requirements.

Requirement	Meaning
Absolute URIs	AM Servers MUST use absolute URIs for all references to resources by properties [AM-3]
Unknown properties and content	AM Servers MAY ignore unknown content and AM clients MUST preserve unknown content. AM Servers may discard such properties and continue the POST or PUT operation without warning to the client. [AM-4]
Resource Operations	AM Servers MUST support resource operations via standard HTTP operations [AM-5]
Update and Delete	AM Servers SHOULD support resource modifications with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications [AM-6]
HTTP If-Match use	AM Servers supporting update and delete of resources MUST support the standard HTTP If-Match header in PUT and DELETE for concurrency protection of resources. [AM-7]
Resource Paging	AM Servers MAY provide paging for resources but only when specifically requested by clients [AM-8]
Partial Resource Representations	AM Servers MAY support requests for a subset of a resource's properties via the oslc.properties URL parameter retrieval via HTTP GET [AM-9]
Partial Update	AM Servers MAY support partial update of resources via the oslc.properties URL parameter retrieval via HTTP PUT and or using [LDPPatch]. [AM-10]
Discovery	AM Servers MAY provide a Service Provider Catalog, MUST provide a Service Provider resource, and MAY provide other forms of discovery described in [OSLCCore3]. [AM-11]
Creation Factories	AM Servers MAY provide creation factories for resource formats that it supports. AM Servers MAY support creation factories for OSLC AM defined resources formatted as application/rdf+xml. AM Servers MAY support creation factories for other formats, and indicate such creation factories with a non-default identifier in the oslc:usage property of the creation factory definition in the service provider document [AM-12]
Query Capabilities	AM Servers MUST provide query capabilities on oslc_am:Resource resources to enable clients to query for resources. AM Servers SHOULD support a query interface for oslc_am:LinkType resources that support a GET for all LinkType resources. Such a GET does not require any simple query syntax parameters. AM Servers MAY support the full query syntax for LinkType resources. [AM-13]
Query Syntax	OSLC query capabilities MUST support the OSLC Core Query Syntax [AM-14]
Delegated Dialogs	AM Services SHOULD offer selection delegated dialogs and MAY offer creation delegated dialogs specified via service provider resource [AM-15]
Resource Preview	AM Services SHOULD offer resource previews for resources that may be referenced by other resources [AM-16]
Authentication	OSLC Services should follow the recommendations for Authentication specified in [OSLCCore3] [AM-17]
Error Responses	AM Servers SHOULD provide error responses using OSLC Core defined error formats [AM-18]
RDF/XML Representations	AM Servers MUST support RDF/XML representations for OSLC Defined Resources [AM-19]
XML Representations	AM Servers MUST support XML representations that conform to the OSLC Core Guidelines for XML [AM-20]
JSON Representations	AM Servers MAY support JSON representations; those which do MUST conform to the OSLC Core Guidelines for JSON [AM-21]
HTML Representations	AM Servers MAY provide HTML representations for GET requests [AM-22]

2.2 Specification Versioning

This specification follows the specification version guidelines given in [OSLCCore3].

2.3 Namespaces

In addition to the namespace URIs and namespace prefixes oslc, rdf, dcterms and foaf defined in the [OSLCCore3], OSLC AM defines the namespace URI of http://open-services.net/ns/am# with a preferred namespace prefix of oslc_am.

2.4 Resource Formats

In addition to the requirements for resource representations in [OSLCCore3], this section outlines further refinements and restrictions.

For HTTP GET/PUT/POST requests on all OSLC AM and OSLC Core defined resource types,

AM Servers MUST support RDF/XML representations with media-type application/rdf+xml. AM Clients should be prepared to deal with any valid RDF/XML document. [AM-23]
AM Servers MUST support XML representations with media-type application/xml. The XML representations MUST follow the guidelines outlined in the OSLC Core Representations Guidance to maintain compatibility with [OSLCCore2]. [AM-24]
AM Servers MAY support JSON representations with media-type application/json. The JSON representations MUST follow the guidelines outlined in the OSLC Core Representations Guidance to maintain compatibility with [OSLCCore2]. [AM-25]

2.5 Resource Operations

OSLC AM Clients MAY include the OSLC Core Version header (OSLC-Core-Version: 2.0) in all HTTP request to OSLC AM Servers as specified in [OSLCCore3]. [AM-26]

OSLC AM Servers MUST support HTTP GET requests on Architecture Management Resources (AMR), with an Accept header of application/rdf+xml, and return the RDF/XML representation of the resource. [AM-27]

OSLC AM Servers SHOULD support HTTP GET requests on Architecture Management Resources (AMR), with an Accept header of an HTML type ( application/html, application/xhtml), and return either an HTML/XHTML representation of the resource or redirect the client to another URL that can (i.e. 302 Redirect). [AM-28]

OSLC AM Servers SHOULD support HTTP GET requests for user interface (UI) preview of Architecture Management Resources (AMR) as defined by [OSLCPreview]. [AM-29]

OSLC AM Servers SHOULD support resource modifications on Architecture Management Resources (AMR) with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications in any way they want. For example a service provider may limit updates to resources to simple link properties of link types already defined in the provider. Modification methods MUST use the If-Match header for concurrency management. Providers MAY discard such properties and continue a PUT operation without warning to the client. [AM-30]

OSLC AM Servers SHOULD support resource modifications on LinkType Resources (LTR) with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications in any way they want. For example a service provider may not support additional properties. Modification methods SHOULD use the If-Match header for concurrency management. [AM-31]

2.6 Authentication

See [OSLCCore3], OSLC AM puts no additional constraints on authentication.

2.7 Error Responses

See [OSLCCore3], OSLC AM puts no additional constraints on error responses

2.8 Pagination

OSLC AM Servers SHOULD support pagination of query results and MAY support pagination of a single resource's properties as defined by [OSLCCore3]. [AM-32]

2.9 Requesting and Updating Properties

2.9.1 Requesting a Subset of Properties

An OSLC AM server MAY support the oslc.properties URL query parameter on an HTTP GET request on individual resource request or a collection of resources by query. If the oslc.properties query parameter is omitted on the request, then all resource properties MUST be provided in the response. [AM-33]

2.9.2 Updating a Subset of Properties

An OSLC AM client MAY request that a subset of a resource's properties be updated by identifying those properties to be modified using the oslc.properties URL parameter on a HTTP PUT request. [AM-34]

2.9.3 Updating Multi-Valued Properties

An OSLC AM Server MAY support updating a subset of a resource's properties by using the [LDPPatch] PATCH method. [AM-35]

For compatibility with [OSLCCore2], an AM Server MAY also support partial update by identifying those properties to be modified using the oslc.properties URL parameter on a HTTP PUT request. [AM-36]

If the parameter oslc.properties contains a valid resource property on the request that is not provided in the content, the server MUST set the resource's property to a null or empty value. If the parameter oslc.properties contains an invalid resource property, then a 409 Conflict MUST be returned. [AM-37]

4. AM Server Capabilities

4.1 Resource Shapes

OSLC AM servers SHOULD support Resource Shapes as defined in [OSLCShapes]. [AM-38]

4.2 Service Provider Resources

OSLC AM Servers MUST provide a ServiceProvider Resource that can be retrieved at a implementation dependent URI. [AM-39]

OSLC AM Servers MUST provide a ServiceProviderCatalog Resource that can be retrieved at a implementation dependent URI. [AM-40]

OSLC AM Servers MUST provide an oslc:serviceProvider property for their defined resources that will be the URI to a ServiceProvider Resource. This does not prevent AM Servers from providing multiple servie provider properties with different values, if the service provider supports multiple OSLC domain specifications, and the resource is applicable to multiple domains. [AM-41]

OSLC AM Servers MUST supply a value of http://open-services.net/ns/am# for the property oslc:domain on either oslc:ServiceProvider or oslc:ServiceProviderCatalog resources. [AM-42]

4.3 Creation Factories

OSLC AM Servers MAY support CreationFactories as defined by [OSLCCore3]. [AM-43]

OSLC AM Servers MAY discard properties it does not recognize and continue the POST operation without warning to the client. The returned resource will contain the accepted properties (and server generated properties like the dcterms:identifer) so clients will be able to confirm if required what was accepted.

If OSLC AM Servers support the creation of resources from the OSLC defined oslc_am:Resource format, there MUST be at least one Creation Factory entry in the Services definition, and its oslc:usage property MUST be set to http://open-services/ns/core#default. The oslc:resourceType MUST be set to http://open-services.net/ns/am#Resource. [AM-44]

If OSLC AM Servers support the creation of resources from a resource other than oslc_am:Resource, there MUST be a separate creation services definition whose oslc:usage property MUST NOT be set to http://open-services/ns/core#default. [AM-45]

4.4 Query Capabilities

OSLC AM Servers SHOULD support the Query Capabilities as defined by [OSLCCore3] for both oslc_am:Resource and oslc_am:LinkType resources. [AM-46]

If the service provider supports query capability for oslc_am:Resource resources, it MUST support the following query parameters: [AM-47]

oslc.where
oslc.searchTerms

OSLC AM Servers SHOULD support query capability for oslc_am:LinkType resources. If supported then AM Servers MUST support a simple GET without any query parameters that returns all link type resources. AM Servers SHOULD support the full OSLC query syntax. [AM-48]

4.5 Delegated UIs

OSLC AM Servers SHOULD support the selection of resources by delegated selection dialogs as defined by [OSLCCore3]. [AM-49]

OSLC AM Servers MAY support the creation of resources by delegated creation dialogs as defined by [OSLCCore3]. [AM-50]

In oslc:Dialog elements, the two optional child elements; oslc:hintWidth and oslc:hintHeight specify the suggested size of the dialog or frame to render the HTML content in. Expected size values are defined by CSS length units. [AM-51]

5. Conformance

Implementations of this specification need to satisfy the following conformance clauses.

Clause Number	Requirement
AM-1	This specification is based on [OSLCCore3]. OSLC AM servers MUST be compliant with both the core specification, MUST follow all the mandatory requirements in the normative sections of this specification, and SHOULD follow all the guidelines and recommendations in both these specifications.
AM-2	An OSLC AM server MUST implement the domain vocabulary defined in OSLC Architecture Management Version 2.1. Part 2: Vocabulary
AM-3	AM Servers MUST use absolute URIs for all references to resources by properties
AM-4	AM Servers MAY ignore unknown content and AM clients MUST preserve unknown content. AM Servers may discard such properties and continue the POST or PUT operation without warning to the client.
AM-5	AM Servers MUST support resource operations via standard HTTP operations
AM-6	AM Servers SHOULD support resource modifications with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications
AM-7	AM Servers supporting update and delete of resources MUST support the standard HTTP If-Match header in PUT and DELETE for concurrency protection of resources.
AM-8	AM Servers MAY provide paging for resources but only when specifically requested by clients
AM-9	AM Servers MAY support requests for a subset of a resource's properties via the oslc.properties URL parameter retrieval via HTTP GET
AM-10	AM Servers MAY support partial update of resources via the oslc.properties URL parameter retrieval via HTTP PUT and or using [LDPPatch].
AM-11	AM Servers MAY provide a Service Provider Catalog, MUST provide a Service Provider resource, and MAY provide other forms of discovery described in [OSLCCore3].
AM-12	AM Servers MAY provide creation factories for resource formats that it supports. AM Servers MAY support creation factories for OSLC AM defined resources formatted as application/rdf+xml. AM Servers MAY support creation factories for other formats, and indicate such creation factories with a non-default identifier in the oslc:usage property of the creation factory definition in the service provider document
AM-13	AM Servers MUST provide query capabilities on oslc_am:Resource resources to enable clients to query for resources. AM Servers SHOULD support a query interface for oslc_am:LinkType resources that support a GET for all LinkType resources. Such a GET does not require any simple query syntax parameters. AM Servers MAY support the full query syntax for LinkType resources.
AM-14	OSLC query capabilities MUST support the OSLC Core Query Syntax
AM-15	AM Services SHOULD offer selection delegated dialogs and MAY offer creation delegated dialogs specified via service provider resource
AM-16	AM Services SHOULD offer resource previews for resources that may be referenced by other resources
AM-17	OSLC Services should follow the recommendations for Authentication specified in [OSLCCore3]
AM-18	AM Servers SHOULD provide error responses using OSLC Core defined error formats
AM-19	AM Servers MUST support RDF/XML representations for OSLC Defined Resources
AM-20	AM Servers MUST support XML representations that conform to the OSLC Core Guidelines for XML
AM-21	AM Servers MAY support JSON representations; those which do MUST conform to the OSLC Core Guidelines for JSON
AM-22	AM Servers MAY provide HTML representations for GET requests
AM-23	AM Servers MUST support RDF/XML representations with media-type `application/rdf+xml`. AM Clients should be prepared to deal with any valid RDF/XML document.
AM-24	AM Servers MUST support XML representations with media-type `application/xml`. The XML representations MUST follow the guidelines outlined in the OSLC Core Representations Guidance to maintain compatibility with [OSLCCore2].
AM-25	AM Servers MAY support JSON representations with media-type `application/json`. The JSON representations MUST follow the guidelines outlined in the OSLC Core Representations Guidance to maintain compatibility with [OSLCCore2].
AM-26	OSLC AM Clients MAY include the OSLC Core Version header (OSLC-Core-Version: 2.0) in all HTTP request to OSLC AM Servers as specified in [OSLCCore3].
AM-27	OSLC AM Servers MUST support HTTP GET requests on Architecture Management Resources (AMR), with an Accept header of `application/rdf+xml`, and return the RDF/XML representation of the resource.
AM-28	OSLC AM Servers SHOULD support HTTP GET requests on Architecture Management Resources (AMR), with an Accept header of an HTML type ( `application/html`, `application/xhtml`), and return either an HTML/XHTML representation of the resource or redirect the client to another URL that can (i.e. 302 Redirect).
AM-29	OSLC AM Servers SHOULD support HTTP GET requests for user interface (UI) preview of Architecture Management Resources (AMR) as defined by [OSLCPreview].
AM-30	OSLC AM Servers SHOULD support resource modifications on Architecture Management Resources (AMR) with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications in any way they want. For example a service provider may limit updates to resources to simple link properties of link types already defined in the provider. Modification methods MUST use the If-Match header for concurrency management. Providers MAY discard such properties and continue a PUT operation without warning to the client.
AM-31	OSLC AM Servers SHOULD support resource modifications on LinkType Resources (LTR) with standard HTTP PUT and DELETE methods. AM Servers MAY limit modifications in any way they want. For example a service provider may not support additional properties. Modification methods SHOULD use the If-Match header for concurrency management.
AM-32	OSLC AM Servers SHOULD support pagination of query results and MAY support pagination of a single resource's properties as defined by [OSLCCore3].
AM-33	An OSLC AM server MAY support the `oslc.properties` URL query parameter on an HTTP GET request on individual resource request or a collection of resources by query. If the `oslc.properties` query parameter is omitted on the request, then all resource properties MUST be provided in the response.
AM-34	An OSLC AM client MAY request that a subset of a resource's properties be updated by identifying those properties to be modified using the `oslc.properties` URL parameter on a HTTP PUT request.
AM-35	An OSLC AM Server MAY support updating a subset of a resource's properties by using the [LDPPatch] `PATCH` method.
AM-36	For compatibility with [OSLCCore2], an AM Server MAY also support partial update by identifying those properties to be modified using the `oslc.properties` URL parameter on a HTTP PUT request.
AM-37	If the parameter `oslc.properties` contains a valid resource property on the request that is not provided in the content, the server MUST set the resource's property to a null or empty value. If the parameter `oslc.properties` contains an invalid resource property, then a `409 Conflict` MUST be returned.
AM-38	OSLC AM servers SHOULD support Resource Shapes as defined in [OSLCShapes].
AM-39	OSLC AM Servers MUST provide a ServiceProvider Resource that can be retrieved at a implementation dependent URI.
AM-40	OSLC AM Servers MUST provide a ServiceProviderCatalog Resource that can be retrieved at a implementation dependent URI.
AM-41	OSLC AM Servers MUST provide an `oslc:serviceProvider` property for their defined resources that will be the URI to a ServiceProvider Resource. This does not prevent AM Servers from providing multiple servie provider properties with different values, if the service provider supports multiple OSLC domain specifications, and the resource is applicable to multiple domains.
AM-42	OSLC AM Servers MUST supply a value of `http://open-services.net/ns/am#` for the property `oslc:domain` on either `oslc:ServiceProvider` or `oslc:ServiceProviderCatalog` resources.
AM-43	OSLC AM Servers MAY support CreationFactories as defined by [OSLCCore3].
AM-44	If OSLC AM Servers support the creation of resources from the OSLC defined `oslc_am:Resource` format, there MUST be at least one Creation Factory entry in the Services definition, and its `oslc:usage` property MUST be set to `http://open-services/ns/core#default`. The `oslc:resourceType` MUST be set to `http://open-services.net/ns/am#Resource`.
AM-45	If OSLC AM Servers support the creation of resources from a resource other than `oslc_am:Resource`, there MUST be a separate creation services definition whose `oslc:usage` property MUST NOT be set to `http://open-services/ns/core#default`.
AM-46	OSLC AM Servers SHOULD support the Query Capabilities as defined by [OSLCCore3] for both `oslc_am:Resource` and `oslc_am:LinkType` resources.
AM-47	If the service provider supports query capability for `oslc_am:Resource` resources, it MUST support the following query parameters:
AM-48	OSLC AM Servers SHOULD support query capability for `oslc_am:LinkType` resources. If supported then AM Servers MUST support a simple GET without any query parameters that returns all link type resources. AM Servers SHOULD support the full OSLC query syntax.
AM-49	OSLC AM Servers SHOULD support the selection of resources by delegated selection dialogs as defined by [OSLCCore3].
AM-50	OSLC AM Servers MAY support the creation of resources by delegated creation dialogs as defined by [OSLCCore3].
AM-51	In `oslc:Dialog` elements, the two optional child elements; `oslc:hintWidth` and `oslc:hintHeight` specify the suggested size of the dialog or frame to render the HTML content in. Expected size values are defined by CSS length units.

Revision	Date	Editor	Changes Made
01	08/24/2018	Jim Amsden	Committee Specification Draft for Public Review published