This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Asset Management Service Description

1.0 Specification


Clients with a need to interact with an Asset Management system need a mechanism for discovering its capabilities, and the URLs used to access those capabilities. There are several aspects to the discovery process. First, clients may need to discover the existence of the Asset Management system itself. Once identifying the system, the clients need to discover the services that are provided within that system. This portion of the OSLC asset management spec addresses the latter of these scenarios, leaving the discovery of the asset management system itself to either manual configuration or a broader network configuration mechanism. Therefore, this spec focuses on how clients will discover the service document associated with that system, and the format of that document.

Refer to the definitions page for descriptions on asset management related terms used here.

Notation and Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119. Domain name examples use RFC2606.

Service Description Resource

A Service Description Resource is an informational resource describing a the contextual configuration needs of a service provider.

The GET method on a Service Description Resource MUST retrieve a Service Description Document. This specification only covers retrieving a Service Description Resource with GET. The behavior of POST, PUT, and DELETE methods on Service Description Resources are not covered in this specification.

Service Description Document

The Service Description Document provides configuration definitions needed by consumers of a service provider.

XML namespace abbreviations used in this specification:

XML Representation Summary: ServiceDescriptor? ? Element
<oslc_asset:ServiceDescriptor rdf:about="anyURI">
Content: {dc:title, dc:description?, dc:contributor?}
Property Representation Presentable
dc:titleThe REQUIRED title string. Note that this element comes from the DC namespace, allowing tools unaware of the change management domain to access this element. Yes
dc:descriptionThe REQUIRED description string. This element comes from the DC namespace, allowing tools completely unaware of the change management domain to access this element. Yes
dc:contributorThe OPTIONAL contributor string. This element comes from the DC namespace, defining the contributing entity of this service implementation.
- dc:titleThe OPTIONAL title string that could be used for display.
- dc:identifier The REQUIRED contributor identifier. This can be of any form but recommend to either be of URN com.{company name}.{product indentifier} or URL forms. This property is to be used by a client application to identify the provider of this service.
- oslc_asset:iconThe OPTIONAL URL to an icon file that represents the provider. This icon should be a favicon format and 16x16 pixels in size
- oslc_asset:home
The OPTIONAL home element when present it MUST have child elements <dc:title> and <oslc_cm:url>. This can be used by service providers to provide a URL to the main Web UI which clients may use to navigate to. There MUST only be one occurrence of this element. Only <dc:title>
- oslc_asset:factory
The OPTIONAL factory element with REQUIRED child elements <dc:title> and <oslc_asset:url>. There may be an optional <oslc_asset:identifier> element that is intended for use in a choice list.Only <dc:title>
- oslc_asset:simpleQueryThe OPTIONAL simple query element with REQUIRED child elements <dc:title> and <oslc_asset:url>. There MUST be only one simpleQuery element.
Only <dc:title>

Providers of this Service Description Document MAY provide additional properties in a non-OSLC namespace.

Presentable text is intended to be seen by users of the client application communicating with the provider of this service. Presentable text, as indicated in the table above, can have multiple entries per translated language supported. The language of each presentable text string will be indicated with the xml:lang attribute.


<?xml version="1.0" encoding="UTF-8"?>
<oslc_asset:ServiceDescriptor rdf:about="https://server:9443/am/oslc/assets/services">
   <dc:title>Asset Management Services</dc:title>
   <dc:description> Asset Manager OSLC Asset Management Service Description  </dc:description>
      <dc:title>Asset Manager</dc:title>

   <!-- Services -->
   <oslc_asset:assets oslc_asset:version="1.0">
      <oslc_asset:home rdf:about="https://server:9443/am/oslc/assets">
         <dc:title>Assets Home</dc:title>

      <!-- Create asset location -->
      <oslc_asset:factory rdf:about="https://server:9443/am/oslc/assets">
         <dc:title>Default location for creation of assets</dc:title>

      <!-- Asset Search -->
      <oslc_asset:simpleQuery rdf:about="https://server:9443/am/oslc/search">
         <dc:title>Assets queries</dc:title>


Topic revision: r15 - 21 Apr 2010 - 17:47:31 - TWikiAdminUser
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback