OSLC Architecture Management Version 3.0. Part 2: Vocabulary defines the OSLC Architecture Management RDF vocabulary terms and resources. This document specifies the standard constraints on those vocabulary terms using OSLC ResourceShapes.
RDF vocabularies define the terms and resources for a domain of interest, life-cycle management in the case of OSLC Architecture Management. These vocabularies are often specified in an open manner, without providing information such as property domain and range assertions, cardinalities, etc. This helps keep the vocabulary applicable for a wide range of uses and furthering integration with other vocabularies.
However, it is often desirable to closed down a vocabulary with specific constraints to facilitate using the vocabulary for a specific purpose. This document specifies the constraints for using the OSLC Architecture Management vocabulary in OSLC. Different sets of constraints may be applied to a vocabulary in order to tailor its use, without overly constraining the vocabulary for other usages.
These constraints apply to the core vocabulary defined in OSLC Architecture Management Version 3.0. Part 2: Vocabulary.
Terminology is based on OSLC Core Overview [[!OSLCCore3]], W3C Linked Data Platform [[!LDP]], W3C's Architecture of the World Wide Web [[WEBARCH]], Hyper-text Transfer Protocol [[!HTTP11]]. Terminology for this specification is defined in part 1 of the multi-part specification.
In addition to the namespace URIs and namespace prefixes
foaf defined in the
OSLC Core specification, OSLC AM defines the namespace URI of
http://open-services.net/ns/am# with a namespace prefix
This specification also uses these namespace prefix definitions:
This section specifies the constraints for the Architecture Management resources. The resource properties are not limited to the ones defined in this specification, AM Servers may provide additional properties. It is recommended that any additional properties exist in their own unique namespace and not use the namespaces defined in these specifications.
An Architecture Management Resource (AMR) is a generic resource format that can be used to represent any type of specific architecture resource such as a UML Class, Use Case, or Business Process Diagram.
A Link Type Resource (LTR) represents type of link that is or can be used when defining links from AM resources. The type has an ID (expressed as a string), whose universally accepted semantics may be defined elsewhere. This resource represents the definition as it is used by this service provider. This resource is meant as a convenience for clients to get a list of known/registered link types with human readable labels and definitions that can be used in client user interfaces when links are being created.
The resource defines the properties rdfs:label and rdfs:comments for the link type URI. The link type URI is
http://open-services.net/ns/am#LinkType via an
rdf:type property. The
remaining properties may be properties of the link type URI, or on a separate resource managed by the service
provider. In the case where the service provider owns the domain of the link type URI these can be the same,
and all properties can be on the same link type URI.
Links from AMR resources are managed in accordance with the OSLC Core Guidance on Links and Relationships. They appear as simple properties in the resource. Links may include inlined values for the target and may include anchor properties on the link itself. AM Servers may support LinkType Resources for clients to get a list of known and acceptable link properties.
Architecture Management servers MUST follow the constraints defined here where required, and with the meanings defined here.
Architecture Management servers MAY provide additional constraints for specific purposes.