Asset Management wiki http://open-services.net/wiki/asset-management Latest changes for the OSLC Asset Management wiki en webmaster@open-services.net webmaster@open-services.net (Lee Reamsnyder) Copyright 2018 Mon, 16 Jul 2018 17:26:32 EDT <![CDATA[OSLC Asset Management 2.0 Specification]]> Sheehan Anderson http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/#When:1348581161 Status: 2.0 Specification - September 25th, 2012

This Version
[[OSLC Asset Management 2.0 Specification]]

Latest Version
http://open-services.net/bin/view/Main/AssetMgSpecificationV2

Previous Version
http://open-services.net/bin/view/Main/AssetMgSpecificationV1

Authors
SheehanAnderson

Contributors
See Contributors section below

Table of Contents

[TOC]

License

http://i.creativecommons.org/l/by/3.0/us/88x31.png This work is licensed under a Creative Commons Attribution License.

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.

Introduction

Asset management systems allow enterprises to catalog, govern, manage, search for, and maintain assets. An asset is anything tangible or intangible that provides value through reference or reuse across a wide audience over an extended period of time. Assets typically have a lifecycle and require a formal process to govern both modification and access. Cataloging assets with standardized taxonomies controls usage and discovery by end users. Assets may also have relationships to and dependencies on other assets.

The term asset in this specification generally refers to either software, documentation, or representations of equipment. While other definitions of an asset may be appropriate, financial instruments are not considered an asset in this specification.

Example software assets may include but are not limited to the final binary output from a software development process, libraries such as a Java archive (JAR) or dynamic-link library (DLL), and installable packages that are distributed through digital distribution platforms such as a repository or app store. Documentation assets may include presentation materials, reports, specifications, blue prints, and instructions. Assets may also represent any type of equipment or structure such as computer hardware, automobiles, pumps, buildings, etc.

Assets are described by a set of properties and zero or more artifacts. An artifact is a file of any type and a set of properties that describe the file.

This specification builds on the Open Services for Lifecycle Collaboration (OSLC) Core v2.0 Specification to define the resources, properties and operations supported by an OSLC Asset Management (OSLC-Asset) provider. Asset Management resources include Assets, Artifacts and supporting resources defined in the OSLC Core specification. The properties defined describe these resources and the relationships between resources. Operations are defined in terms of HTTP methods and MIME type handling. The resources, properties and operations defined do not form a comprehensive interface to Asset Management, but instead target specific integration use cases documented by the OSLC-Asset workgroup.

This specification also defines how Assets and Artifacts are represented in OSLC Services. The Asset Resource is a set of properties for an Asset, and includes properties that describe Artifacts of an Asset.

Asset Management Resources Overview

This version of the OSLC Asset specification is demonstrated in the [[OSLC Asset Management 2.0 Samples | version 2.0 samples]].

Terminology

Asset Consumer - A tool or user that performs asset searching and retrieval activities outlined in the search and retrieve scenarios.

Asset Resource - An Asset Resource has a set of properties representing an asset. These properties include such things as name, description, classification, and the Artifact properties for an Asset.

Asset Query Resource - When filtering using simple query, the representation of a list of Asset Resources.

Asset Submitter - A tool or user that performs asset preparation activities outlined in the publish scenario.

Artifact - This term refers to the properties that describe an Asset Artifact and potentially the Artifact Media referenced by this Artifact. An Asset may have zero or more Artifacts.

Artifact Fragment - Fragment within an Asset Resource that describes an Artifact Media Resource. The term fragment is associated with an Artifact instead of resource because Artifacts are referenced by the Asset’s URL with a fragment identifier. Artifacts are considered to be contained within the asset and when the asset is deleted the artifact is also deleted. While two different Artifacts in separate Assets may reference to the same Artifact Media Resource, two different Assets may not contain the same Artifact.

Artifact Media Resource - The Artifact Media Resource represents the actual artifact content. The content can be a presentation, a test case, a binary software component, or any other kind of file.

Property - An attribute of a resource. Typically a property is a name/value pair that describes a certain aspect of the resource. For example, an asset has many properties such as the asset title, subject/short description, version.

Service Provider - An implementation of the OSLC Asset Management specification as a server. OSLC Asset Management clients consume these services.

Work product - This term is often used interchangeably with ‘artifact’ or ‘file’. An asset may have zero or more work products.

Base Requirements

Compliance

This specification is based on OSLC Core Specification. OSLC Asset Management 2.0 consumers and service providers MUST be compliant with both the core specification and this Asset Management specification, and SHOULD follow all the guidelines and recommendations in both these specifications.

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

Requirement Level Meaning
Unknown properties and content MAY / MUST OSLC services MAY ignore unknown content and OSLC clients MUST preserve unknown content
Resource Operations MUST OSLC service MUST support resource operations via standard HTTP operations
Resource Paging MAY OSLC services MAY provide paging for resources but only when specifically requested by client
Partial Resource Representations MAY / MUST OSLC services MUST support request for a subset of a resource’s properties via the oslc.properties URL parameter retrieval via HTTP GET and MAY support via HTTP PUT
Partial Update MAY OSLC services MAY support partial update of resources using patch semantics
Service Provider Resources MAY / MUST OSLC service providers MAY provide a Service Provider Catalog and MUST provide a Service Provider resource
Creation Factories MUST OSLC service providers MUST provide creation factories to enable resource creation via HTTP POST
Query Capabilities MUST OSLC service providers MUST provide query capabilities to enable clients to query for resources
Query Syntax MUST OSLC query capabilities MUST support the OSLC Core Query Syntax and MAY use other query syntax
Delegated UI Dialogs MUST OSLC Services MUST offer delegated UI dialogs (creation and selections) specified via service provider resource
UI Preview SHOULD OSLC Services SHOULD offer UI previews for resources that may be referenced by other resources
HTTP Basic Authentication MAY OSLC Services MAY support Basic Auth and should do so only over HTTPS
OAuth Authentication SHOULD OSLC Services SHOULD support OAuth and can indicate the required OAuth URLs via the service provider resource
Error Responses MAY OSLC Services MAY provide error responses using Core defined error formats
RDF/XML Representations MUST OSLC services MUST provide an RDF/XML representation for HTTP GET requests and MUST support RDF/XML representations on POST and PUT requests.
XML Representations MAY OSLC services MAY provide a XML representation for HTTP GET, POST and PUT requests that conform to the Core Guidelines for XML.
JSON Representations SHOULD OSLC services SHOULD provide JSON representations for HTTP GET, POST and PUT requests that conform to the Core Guidelines for JSON
HTML Representations SHOULD OSLC services SHOULD provide HTML representations for HTTP GET requests

Specification Versioning

See OSLC Core Specification Versioning section.

Service providers that support the resource formats and services in this specification MUST use HTTP response header of OSLC-Core-Version with a value of 2.0 and OSLC-Asset-Version with a value of 2.0. Consumers MAY request formats and services defined in this document by providing a HTTP request header of OSLC-Core-Version with a value of 2.0. See section below on Version Compatibility with OSLC Asset 1.0 Specifications.

Namespaces

In addition to the namespace URIs and namespace prefixes oslc, rdf, dcterms and foaf defined in the OSLC Core specification, OSLC Asset Management defines the namespace URI of http://open-services.net/ns/asset# with a namespace prefix of oslc_asset

Resource Formats

In addition to the requirements for OSLC Core Resource Formats section, this section outlines further refinements and restrictions.

For HTTP GET requests on all OSLC Asset Management and OSLC Core defined resource types,

  • Asset Management Providers MUST provide RDF/XML representations, SHOULD provide JSON representations, and MAY provide XML representations. The XML and JSON representations SHOULD follow the guidelines outlined in the OSLC Core Representations Guidance.
  • Asset Management Consumers requesting RDF/XML SHOULD be prepared for any valid RDF/XML document. Asset Management Consumers requesting XML or JSON SHOULD be prepared for representations that follow the guidelines outlined in the OSLC Core Representations Guidance.
  • Asset Management Providers SHOULD support an [X]HTML representation and a user interface (UI) preview as defined by UI Preview Guidance

For HTTP PUT/POST request formats for resource type of Asset:

  • Asset Management Providers MUST accept RDF/XML representations, SHOULD accept JSON representations, and MAY accept XML representations. Asset Management Providers accepting RDF/XML SHOULD be prepared for any valid RDF/XML document. For XML or JSON, Asset Management Providers SHOULD be prepared for representations that follow the guidelines outlined in the OSLC Core Representations Guidance.

For HTTP GET response formats for Query requests,

Asset Management Providers MUST provide RDF/XML representations, SHOULD provide JSON and Atom Syndication Format XML representations, and MAY provide XML representations.

When Asset Management Consumers request:

  • application/rdf+xml Asset Management Providers MUST respond with RDF/XML representation without restrictions.
  • application/json Asset Management Providers SHOULD respond with JSON representation as defined in the OSLC Core Representations Guidance.
  • application/xml Asset Management Provider MAY respond with OSLC-defined abbreviated XML representation as defined in the OSLC Core Representations Guidance
  • application/atom+xml Asset Management Provider SHOULD respond with Atom Syndication Format XML representation as defined in the OSLC Core Representations Guidance
  • The Atom Syndication Format XML representation SHOULD use RDF/XML representation without restrictions for the atom:content entries representing the resource representations.

See Query Capabilities for additional information when Resource Shapes affect representation.

Content Negotiation

OSLC Core Guidance clearly points to RDF representations (and specifically RDF/XML) as a convention that all OSLC Provider implementations minimally provide and accept. OSLC Asset Provider implementations are strongly encouraged to adopt this convention. Future versions of this specification are expected to require RDF representations for all operations and relax requirements for specialized XML representations.

XML Representation - identified by the application/xml content type. Format representation rules are outlined in Core OSLC Core Resource Formats section

RDF/XML Representation - identified by the application/rdf+xml content type. No additional guidance is given. The OSLC Core describes an algorithm for generating consistent formats that are used as examples only.

JSON Representation - identified by the application/json content type. Format representation rules are outlined in Core OSLC Core Resource Formats section.

Atom Syndication Format XML Representation - identified by the application/atom+xml content type. Format representation rules are outlined in Core OSLC Core Resource Formats section.

Authentication

See OSLC Core Authentication section. Asset Management puts no additional constraints on authentication.

Error Responses

See OSLC Core Error Responses section. Asset Management puts no additional constraints on error responses.

Pagination

OSLC Asset service providers SHOULD support pagination of query results and MAY support pagination of a single resource’s properties as defined by the OSLC Core Specification.

Requesting and Updating Properties

Requesting a Subset of Properties

A client MAY request a subset of a resource’s properties as well as properties from a referenced resource. In order to support this behavior a service provider MUST support the oslc.properties and oslc.prefix URL parameter on a HTTP GET request on individual resource request or a collection of resources by query. If the oslc.properties parameter is omitted on the request, then all resource properties MUST be provided in the response.

Updating a Subset of Properties

A 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.

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.

Labels for Relationships

Asset relationships to other resources are represented as properties whose values are the URI of the object or target resource. When an Asset relationship property is to be presented in a user interface, it may be helpful to provide an informative and useful textual label for that relationship instance. (This in addition to the relationship property URI and the object resource URI, which are also candidates for presentation to a user.) To this end, OSLC providers MAY support a dcterms:title link property in Asset resource representations, using the anchor approach outlined in the OSLC Core Links Guidance. In addition to the textual label, the Asset resource definition defines several properties that can be used to describe the relationship from one Asset resource to another Asset resource.

RDF/XML and XML example using reified statement:

<rdf:RDF 
     xmlns:dcterms="http://purl.org/dc/terms/" 
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:oslc_asset="http://open-services.net/ns/asset#">

    <oslc_asset:Asset rdf:about="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0">
         <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
    </oslc_asset:Asset>

    <rdf:Description rdf:about="#relationship1">
        <dcterms:title>Build Configuration</dcterms:title>
   </rdf:Description>
</rdf:RDF>

Custom Properties

Asset management providers SHOULD allow consumers to define custom properties. If providers allow consumers to define custom properties, they MUST allow the consumer to optionally specify an HTTP URI for that data element, and the specified URI MUST be used in the RDF representation of all resources that contain the data element. The specified URI MAY be part of an industry standard such as DC, FOAF, or OSLC, or it MAY be defined by the user’s organization. If the URI is defined by the user’s organization, then they SHOULD make it dereferencable as per the W3C Best Practices for Publishing RDF Vocabularies.

If the user does not specify the optional URI, then the provider MUST use a default generated HTTP URI. The generated URI SHOULD be as human-readable as possible. One method for achieving human-readability is to apply a human-friendly name mangling algorithm to the user-defined label for the data element. The tool SHOULD make the generated URI dereferencable as per the W3C Best Practices for Publishing RDF Vocabularies. The published RDF vocabulary SHOULD include any relevant descriptive information provided the user as part of the data element definition, e.g. the label and description.

OSLC Asset Management Resource Definitions

Asset

An Asset is anything tangible or intangible that is capable of being owned or controlled to produce value, and is held to have positive economic value. This includes not only software products, but also buildings, servers, automobiles, pumps, oil wells, etc. These properties include such things as name, description, classification, and the Artifact properties of an Asset.

The Asset resource properties are not limited to the ones defined in this specification, service providers 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.

Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Core: Common Properties
dcterms:identifier zero-or-one True String n/a n/a A unique identifier for a resource. Assigned by the service provider when a resource is created.
dcterms:title exactly-one unspecified XMLLiteral n/a n/a Short name identifying a resource, often used as an abbreviated identifier for presentation to end-users. SHOULD include only content that is valid inside an XHTML element.
dcterms:description zero-or-one unspecified XMLLiteral n/a n/a Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML element.
dcterms:creator zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case
dcterms:contributor zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any The person(s) who are responsible for this asset. (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp latest resource modification (reference: Dublin Core).
rdf:type zero-or-many unspecified Resource Reference n/a The resource type URIs. One reference should have the value of http://open-services.net/ns/asset#Asset.
oslc:serviceProvider zero-or-many unspecified Resource Reference oslc:ServiceProvider The scope of a resource is a URI for the resource’s OSLC Service Provider.
oslc:instanceShape zero-or-one unspecified Resource Reference oslc:ResourceShape Resource Shape that provides hints as to resource property value-types and allowed values.
Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Asset: Start of additional properties
oslc_asset:guid zero-or-one unspecified String n/a n/a An identifier for the asset. Assigned by the service provider when a resource is created. Different versions of the same asset will share the same identifier.
oslc_asset:version zero-or-one unspecified String n/a n/a The version of the asset. Possible values may include ‘1.0’, ‘2.0’, etc.
dcterms:abstract zero-or-one unspecified XMLLiteral n/a n/a Short description (reference: Dublin Core) or often a single line summary of the resource
dcterms:type zero-or-one unspecified Resource Reference n/a The type of the asset based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:state zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any Used to indicate the state of the asset based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:categorization zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any A categorization to classify an asset. The category schema values are defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:manufacturer zero-or-one unspecified String n/a n/a The name of the asset manufacturer.
oslc_asset:model zero-or-one unspecified String n/a n/a The value of the asset model.
oslc_asset:serialNumber zero-or-one unspecified String n/a n/a The serial number assigned by the asset manufacturer.
oslc_asset:tag zero-or-many unspecified String n/a n/a Specifies the asset tag value for an Asset. Asset tags are typically human readable labels. For hardware assets, these tags are durable, securely attached to equipment, and may also be readable by barcode and/or RFID.
oslc_asset:artifact zero-or-many unspecified Local Resource Inline oslc_asset:Artifact An Artifact fragment contained in this Asset resource.
oslc_asset:artifactFactory exactly-one unspecified Resource Reference any Resource URI used to post new artifacts to the asset.
Prefixed Name Occurs Read-only Value-type Representation Range Description
Relationship Properties: This grouping of properties are used to identify relationships between resources managed by the current or other OSLC Service Providers
dcterms:relation zero-or-many False Resource Reference any This relationship is loosely coupled and has no specific meaning. Details about this relationship may be included in a reified statement.
Prefixed Name Occurs Read-only Value-type Representation Range Description
Related Resource Reified Statement Properties: This grouping of properties is used to provide additional details about a relationship in a reified statement
oslc_asset:relationshipType zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any The type of this relationship from the perspective of the dcterms:relation resource based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
dcterms:creator zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any Creator or creators of the relationship (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of the relationship creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp of the latest relationship modification (reference: Dublin Core).
oslc_asset:state zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any Used to indicate the state of the relationship based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.

Artifact

An Artifact is a fragment within an asset resource that describes an Artifact Media Resource. An artifact fragment may only be updated though an Asset resource and it is not possible to perform operations directly on the Artifact fragment

The Artifact fragment properties are not limited to the ones defined in this specification, service providers 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.

Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Artifact Fragment: The grouping of properties that define an artifact
rdf:type zero-or-many unspecified Resource Reference n/a The resource type URIs. One reference should have the value of http://open-services.net/ns/asset#Artifact.
dcterms:title exactly-one unspecified XMLLiteral n/a n/a The name of the artifact. Title (reference: Dublin Core) of the resource represented in text XHTML content. SHOULD include only content that is valid inside an XHTML element.
oslc:label zero-or-one unspecified XMLLiteral n/a n/a The label of the artifact. Subject (reference: Dublin Core) an abbreviated presentation for the end-users. SHOULD include only content that is valid inside an XHTML element.
oslc_asset:content exactly-one unspecified Resource Reference Artifact Media The media resource reference URI (the artifact bytes).
dcterms:format zero-or-one unspecified String n/a n/a The mime type of the artifact media resource.
oslc_asset:size zero-or-one True Integer n/a n/a The size of the artifact media resource in bytes.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp last latest resource modification (reference: Dublin Core).

Artifact Media

The artifact media represents the actual content of an artifact. The URI for the artifact media resource is defined by the oslc_asset:content property of an artifact fragment within an asset resource.

A client may publish a new artifact to an asset making a POST request to the asset’s artifact factory URI as defined by the oslc_asset:artifactFactory property of the asset resource. The request MUST contain an oslc_asset.name header indicating the path and name of the new artifact and the body of the POST MUST contain the contents of the artifact. A successful response from the provider MUST return a status code of 201 and a Location Header indicating the URI of the Media Resource. In addition, the provider MUST add a new artifact fragment to the asset and fill in the mandatory properties including size, and creation time. The client may later update the non-read only properties of this fragment.

See the Publish an artifact sample for additional details.

Providers MUST also support URI artifacts. URI artifacts do not contain content, but instead the oslc_asset:content property’s value is a URI external to the asset. To create a URI artifact, clients POST an artifact resource to the artifact factory URI. The request MUST contain an oslc_asset.name header indicating the path and name of the new artifact URI. A successful response from the provider MUST return a status code of 201 and a Location Header indicating the URI of the artifact URI. In addition, the provider MUST add a new artifact fragment to the asset and fill in the mandatory properties such as creation time. The client may later update the non-read only properties of this fragment.

See the Publish a URI artifact sample for additional details.

Asset Management Service Provider Capabilities

Service Discovery and Description

OSLC Asset Management service providers MUST provide a Service Provider Resource that can be retrieved at a implementation dependent URI.

OSLC Asset Management service providers MAY provide a Service Provider Catalog Resource that can be retrieved at a implementation dependent URI.

OSLC Asset Management service providers MUST provide a oslc:serviceProvider property for their defined resources that will be the URI to a Service Provider Resource.

OSLC Asset Management service providers MUST supply a value of http://open-services.net/ns/asset# for the property oslc:domain on either oslc:Service or oslc:ServiceProviderCatalog resources.

Creation Factories

OSLC Asset Management service providers MUST support Creation Factories and list them in the Service Provider Resource as defined by OSLC Core. OSLC Asset Management service providers SHOULD support Resource Shapes for Creation Factories as defined in OSLC Core Specification

Query Capabilities

OSLC Asset Management service providers MUST support the Query Capabilities as defined by OSLC Core. OSLC Asset Management service providers SHOULD support Resource Shapes for Query Capability as defined in OSLC Core Specification

The Query Capability MUST support these parameters:

  • oslc.where
  • oslc.select
  • oslc.properties
  • oslc.prefix

If shape information is NOT present with the Query Capability, service providers SHOULD use these default properties to contain the result:

Delegated User Interface Dialogs

OSLC Asset Management service providers SHOULD support the selection of resources by delegated web-based user interface dialogs Delegated UIs as defined by OSLC Core.

OSLC Asset Management service providers MAY support the creation of resources by delegated web-based user interface dialogs Delegated UIs as defined by OSLC Core.

OSLC Asset Management service providers MAY support the pre-filling of creation dialogs based on the definition at Delegated UIs.

The service providers supports the delegated UIs as follows:

Asset Management Resource Selection Creation
Asset SHOULD MAY

Version Compatibility with 1.0 Specifications

The goal is to provide a smooth transition to 2.0 for both Consumers and Providers. This section will clarify the usage of 1.0 media types so that Providers can support both 1.0 and 2.0 Consumers when HTTP requests are made for a resource with the same URI.

Media Types

For an Asset Resource format identification of RDF/XML and XML, the media type used for this representation SHOULD be application/rdf+xml or application/xml.

For an Asset Resource format identification of JSON, the media type used for this representation SHOULD be application/json.

Appendix A: Samples

(this section is informative)

See [[OSLC Asset Management 2.0 Samples]].

Appendix B: Resource Shapes

(this section is informative)

See [[OSLC Asset Management 2.0 Appendix B: Resource Shapes]]

Appendix C: Notices and References

Contributors

  • Brad Sandler (IBM)
  • Dave Johnson (IBM)
  • Edwin Freekenhorst (Shell)
  • Eric Bordeau (IBM)
  • Gili Mendel (IBM; OSLC Asset Management Lead)
  • Grant Larsen (IBM)
  • Hari Padmanabhan (IBM)
  • Jaimin Patel (WebLayers)
  • John Favazza (WebLayers)
  • Kevin Bauer (IBM)
  • Randy Lexvold (the Emphasys Group)
  • Ren Renganathan (Citigroup)
  • Scott Bosworth (IBM)
  • Sheehan Anderson (IBM)
  • Srimanth Gunturi (IBM)

Reporting Issues on the Specification

The working group participants who author and maintain this working draft specification, monitor a distribution list where issues or questions can be raised, see Asset Management Mailing List

Also the issues found with this specification and their resolution can be found at [[OSLC Asset Management 2.0 specification issues]].

Intellectual Property Covenant

The members of the Working Group (or as appropriate, their employers) have documented a Patent Non-Assertion Covenant for implementations of the Asset Management 2.0 Specification, as described in the open-services.net Terms of Use. Details of the Covenant may be found here.

References

]]> Tue, 25 Sep 2012 09:52 EDT <![CDATA[index]]> Sheehan Anderson http://open-services.net/wiki/asset-management/ http://open-services.net/wiki/asset-management/#When:1348581012 [TOC]

Introduction

The goal of this effort is to define a common set of resources, formats and RESTful services for the use in Asset Management tools and use by ALM and PLM tools.

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

Approach

The specifications will be developed iteratively by first prioritizing scenarios and focusing on a minimal set of key scenarios. Once these scenarios have been satisfied by specification and proof of implementation, more scenarios will be considered.

Status

[[Meeting agendas and minutes]]

Specifications

2.0 (Finalization)

Document Version Status
[[OSLC Asset Management 2.0 Specification]] 2.0 complete/finalized
[[OSLC Asset Management 2.0 specification issues]] 2.0 Catalog of Spec Issues

1.0 (Finalized)

Document Version Status
OSLC Asset Management Specification 1.0 1.0 complete/finalized
OSLC Asset Management 1.0 Specification ISSUES 1.0 Catalog of Spec Issues

Supporting Documents

Document Version Status
[[OSLC Asset Management Vocabulary RDFS Vocabulary]] 2.0 | complete/finalized
Asset Management Use Case 2.0 draft
OSLC Service Provider Catalog 1.0 specification
Asset Management Build System Use Cases 1.0 convergence
Asset Management Human Interaction Use Cases 1.0 future
Context: Lifecycles 1.0 future

Milestones

Note: iterative specification validation will be occurring as the drafts evolve before finalization. The goal is to not develop the specification in abstract; but to do it in parallel with implementations. We will identify the integration opportunities to validate the spec in order for it to be finalized.

Complete Scenario: this means we have documented on the wiki and agreed to the scenarios for which the REST API will be specified/implemented
Start Draft Specs: this means we have sufficient context from the scenarios to begin describing the REST API specs; as the specs mature, so implementing the RETS API based on the specs can begin as well
Start Convergence: this means the spec is ‘near final’ and final polishing activities begin

Scenario Complete Scenario Start Draft Specs Start Convergence Finalize Spec
Publish 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010
Search 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010
Retrieve 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010

Resources

[[Implementation Reports]]

Mailing Lists

General Open Services
Asset Management workgroup

]]> Tue, 25 Sep 2012 09:50 EDT <![CDATA[Meeting agenda and minutes 11 September 2012]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/ http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/#When:1347482135 Date: Tuesday, 11 September 2012
Time: 1:00 PM EDT
Contact Sheehan Anderson if you’d like to participate.

Agenda

  • Steering Committee Approval.
  • New meeting schedule.

Minutes

  • Now that the 2.0 specification is just waiting for final approval, meetings will be held bi-monthly.

Action Items

Attendees

IBM

  • Gili Mendel
  • Sheehan Anderson
]]> Wed, 12 Sep 2012 16:35 EDT <![CDATA[Meeting agenda and minutes 11 September 2012]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/ http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/#When:1347482120 Date: Tuesday, 11 September 2012
Time: 1:00 PM EDT
Contact Sheehan Anderson if you’d like to participate.

Agenda

  • Steering Committee Approval.
  • New meeting schedule.

Minutes - Now that the 2.0 specification is just waiting for final approval, meetings will be held bi-monthly.

Action Items

Attendees

IBM

  • Gili Mendel
  • Sheehan Anderson
]]> Wed, 12 Sep 2012 16:35 EDT <![CDATA[Meeting agenda and minutes 11 September 2012]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/ http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-11-September-2012/#When:1347376804 Date: Tuesday, 11 September 2012
Time: 1:00 PM EDT
Contact Sheehan Anderson if you’d like to participate.

Agenda

  • Steering Committee Approval.
  • New meeting schedule.

Minutes

Action Items

Attendees

IBM

  • Gili Mendel
  • Sheehan Anderson
]]> Tue, 11 Sep 2012 11:20 EDT <![CDATA[Meeting agendas and minutes]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/ http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/#When:1347376664 Meeting Agendas and Minutes for Asset Management

Meetings are held bi-weekly on Tuesday.

Time: 1:00 PM EDT

(contact Gili Mendel if you’d like to participate)

2.0 Meetings

11 September 2012

28 August 2012

14 August 2012

19 June 2012

8 May 2012

10 April 2012

13 March 2012

28 February 2012

14 February 2012

7 February 2012

31 January 2012

17 January 2012

03 January 2012

25 October 2011

11 October 2011

27 September 2011

31 August 2011

17 August 2011

3 August 2011

28 July 2011

6 July 2011

23 June 2011

25 May 2011

11 May 2011

28 July 2010

30 June 2010

26 May 2010

1.0 Meetings

17 Feb 2010

9 Sep 2009

26 Aug 2009

12 Aug 2009

29 July 2009

15 July 2009

1 July 2009

17 June 2009

]]> Tue, 11 Sep 2012 11:17 EDT <![CDATA[Meeting agendas and minutes]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/ http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/#When:1346176008 Meeting Agendas and Minutes for Asset Management

Meetings are held bi-weekly on Tuesday.

Time: 1:00 PM EDT

(contact Gili Mendel if you’d like to participate)

2.0 Meetings

28 August 2012

14 August 2012

19 June 2012

8 May 2012

10 April 2012

13 March 2012

28 February 2012

14 February 2012

7 February 2012

31 January 2012

17 January 2012

03 January 2012

25 October 2011

11 October 2011

27 September 2011

31 August 2011

17 August 2011

3 August 2011

28 July 2011

6 July 2011

23 June 2011

25 May 2011

11 May 2011

28 July 2010

30 June 2010

26 May 2010

1.0 Meetings

17 Feb 2010

9 Sep 2009

26 Aug 2009

12 Aug 2009

29 July 2009

15 July 2009

1 July 2009

17 June 2009

]]> Tue, 28 Aug 2012 13:46 EDT <![CDATA[Meeting agenda and minutes 28 August 2012]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-28-August-2012/ http://open-services.net/wiki/asset-management/Meeting-agenda-and-minutes-28-August-2012/#When:1346175928 Date: Tuesday, 28 August 2012
Time: 1:00 PM EDT
Contact Sheehan Anderson if you’d like to participate.

Agenda

  • Check out the new wiki. Make sure pages have been migrated correctly.

Minutes

  • Confirmed that the 2.0 specification has been successfully migrated to the wiki
  • Steering Committee Approval
    We are waiting to hear from the steering committee regarding final approval of the asset specification

Action Items

Attendees

IBM

  • Gili Mendel
  • Sheehan Anderson
]]> Tue, 28 Aug 2012 13:45 EDT <![CDATA[Meeting agendas and minutes]]> Sheehan Anderson http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/ http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/#When:1346169711 Meeting Agendas and Minutes for Asset Management

Meetings are held bi-weekly on Tuesday.

Time: 1:00 PM EDT

(contact Gili Mendel if you’d like to participate)

2.0 Meetings

28 August 2012

14 August 2012

19 June 2012

8 May 2012

10 April 2012

13 March 2012

28 February 2012

14 February 2012

7 February 2012

31 January 2012

17 January 2012

03 January 2012

25 October 2011

11 October 2011

27 September 2011

31 August 2011

17 August 2011

3 August 2011

28 July 2011

6 July 2011

23 June 2011

25 May 2011

11 May 2011

28 July 2010

30 June 2010

26 May 2010

1.0 Meetings

17 Feb 2010

9 Sep 2009

26 Aug 2009

12 Aug 2009

29 July 2009

15 July 2009

1 July 2009

17 June 2009

]]> Tue, 28 Aug 2012 12:01 EDT <![CDATA[index]]> OSLC Administrator http://open-services.net/wiki/asset-management/ http://open-services.net/wiki/asset-management/#When:1346100595 [TOC]

Introduction

The goal of this effort is to define a common set of resources, formats and RESTful services for the use in Asset Management tools and use by ALM and PLM tools.

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

Approach

The specifications will be developed iteratively by first prioritizing scenarios and focusing on a minimal set of key scenarios. Once these scenarios have been satisfied by specification and proof of implementation, more scenarios will be considered.

Status

[[Meeting agendas and minutes]]

Specifications

2.0 (Finalization)

Document Version Status
[[OSLC Asset Management 2.0 Specification]] 2.0 finalization
[[OSLC Asset Management 2.0 specification issues]] 2.0 Catalog of Spec Issues

1.0 (Finalized)

Document Version Status
OSLC Asset Management Specification 1.0 1.0 complete/finalized
OSLC Asset Management 1.0 Specification ISSUES 1.0 Catalog of Spec Issues

Supporting Documents

Document Version Status
[[OSLC Asset Management Vocabulary RDFS Vocabulary]] 2.0 | finalization
Asset Management Use Case 2.0 early draft
OSLC Service Provider Catalog 1.0 specification
Asset Management Build System Use Cases 1.0 convergence
Asset Management Human Interaction Use Cases 1.0 future
Context: Lifecycles 1.0 future

Milestones

Note: iterative specification validation will be occurring as the drafts evolve before finalization. The goal is to not develop the specification in abstract; but to do it in parallel with implementations. We will identify the integration opportunities to validate the spec in order for it to be finalized.

Complete Scenario: this means we have documented on the wiki and agreed to the scenarios for which the REST API will be specified/implemented
Start Draft Specs: this means we have sufficient context from the scenarios to begin describing the REST API specs; as the specs mature, so implementing the RETS API based on the specs can begin as well
Start Convergence: this means the spec is ‘near final’ and final polishing activities begin

Scenario Complete Scenario Start Draft Specs Start Convergence Finalize Spec
Publish 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010
Search 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010
Retrieve 21 Oct 2009 26 Aug 2009 Feb 2010 17 March 2010

Resources

[[Implementation Reports]]

Mailing Lists

General Open Services
Asset Management workgroup

]]> Mon, 27 Aug 2012 16:49 EDT <![CDATA[OSLC Asset Management 2.0 Specification]]> OSLC Administrator http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Specification/#When:1346098746 2.0 FINALIZATION DRAFT. This current draft is intended for review during finalization. You can help by reviewing it carefully and raising issues for discussion on the OSLC Asset Management mailing list. For issues regarding this specification and their resolution, see [[OSLC Asset Management 2.0 specification issues]]. The specification will be final once the first Asset Management provider implementation is completed. This is currently in progress and scheduled for completion in April 2012.

Status: 2.0 Specification - April 10th, 2012

This Version
[[OSLC Asset Management 2.0 Specification]]

Latest Version
http://open-services.net/bin/view/Main/AssetMgSpecificationV2

Previous Version
http://open-services.net/bin/view/Main/AssetMgSpecificationV1

Authors
SheehanAnderson

Contributors
See Contributors section below

Table of Contents

[TOC]

License

http://i.creativecommons.org/l/by/3.0/us/88x31.png This work is licensed under a Creative Commons Attribution License.

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.

Introduction

Asset management systems allow enterprises to catalog, govern, manage, search for, and maintain assets. An asset is anything tangible or intangible that provides value through reference or reuse across a wide audience over an extended period of time. Assets typically have a lifecycle and require a formal process to govern both modification and access. Cataloging assets with standardized taxonomies controls usage and discovery by end users. Assets may also have relationships to and dependencies on other assets.

The term asset in this specification generally refers to either software, documentation, or representations of equipment. While other definitions of an asset may be appropriate, financial instruments are not considered an asset in this specification.

Example software assets may include but are not limited to the final binary output from a software development process, libraries such as a Java archive (JAR) or dynamic-link library (DLL), and installable packages that are distributed through digital distribution platforms such as a repository or app store. Documentation assets may include presentation materials, reports, specifications, blue prints, and instructions. Assets may also represent any type of equipment or structure such as computer hardware, automobiles, pumps, buildings, etc.

Assets are described by a set of properties and zero or more artifacts. An artifact is a file of any type and a set of properties that describe the file.

This specification builds on the Open Services for Lifecycle Collaboration (OSLC) Core v2.0 Specification to define the resources, properties and operations supported by an OSLC Asset Management (OSLC-Asset) provider. Asset Management resources include Assets, Artifacts and supporting resources defined in the OSLC Core specification. The properties defined describe these resources and the relationships between resources. Operations are defined in terms of HTTP methods and MIME type handling. The resources, properties and operations defined do not form a comprehensive interface to Asset Management, but instead target specific integration use cases documented by the OSLC-Asset workgroup.

This specification also defines how Assets and Artifacts are represented in OSLC Services. The Asset Resource is a set of properties for an Asset, and includes properties that describe Artifacts of an Asset.

Asset Management Resources Overview

This version of the OSLC Asset specification is demonstrated in the [[OSLC Asset Management 2.0 Samples | version 2.0 samples]].

Terminology

Asset Consumer - A tool or user that performs asset searching and retrieval activities outlined in the search and retrieve scenarios.

Asset Resource - An Asset Resource has a set of properties representing an asset. These properties include such things as name, description, classification, and the Artifact properties for an Asset.

Asset Query Resource - When filtering using simple query, the representation of a list of Asset Resources.

Asset Submitter - A tool or user that performs asset preparation activities outlined in the publish scenario.

Artifact - This term refers to the properties that describe an Asset Artifact and potentially the Artifact Media referenced by this Artifact. An Asset may have zero or more Artifacts.

Artifact Fragment - Fragment within an Asset Resource that describes an Artifact Media Resource. The term fragment is associated with an Artifact instead of resource because Artifacts are referenced by the Asset’s URL with a fragment identifier. Artifacts are considered to be contained within the asset and when the asset is deleted the artifact is also deleted. While two different Artifacts in separate Assets may reference to the same Artifact Media Resource, two different Assets may not contain the same Artifact.

Artifact Media Resource - The Artifact Media Resource represents the actual artifact content. The content can be a presentation, a test case, a binary software component, or any other kind of file.

Property - An attribute of a resource. Typically a property is a name/value pair that describes a certain aspect of the resource. For example, an asset has many properties such as the asset title, subject/short description, version.

Service Provider - An implementation of the OSLC Asset Management specification as a server. OSLC Asset Management clients consume these services.

Work product - This term is often used interchangeably with ‘artifact’ or ‘file’. An asset may have zero or more work products.

Base Requirements

Compliance

This specification is based on OSLC Core Specification. OSLC Asset Management 2.0 consumers and service providers MUST be compliant with both the core specification and this Asset Management specification, and SHOULD follow all the guidelines and recommendations in both these specifications.

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

Requirement Level Meaning
Unknown properties and content MAY / MUST OSLC services MAY ignore unknown content and OSLC clients MUST preserve unknown content
Resource Operations MUST OSLC service MUST support resource operations via standard HTTP operations
Resource Paging MAY OSLC services MAY provide paging for resources but only when specifically requested by client
Partial Resource Representations MAY / MUST OSLC services MUST support request for a subset of a resource’s properties via the oslc.properties URL parameter retrieval via HTTP GET and MAY support via HTTP PUT
Partial Update MAY OSLC services MAY support partial update of resources using patch semantics
Service Provider Resources MAY / MUST OSLC service providers MAY provide a Service Provider Catalog and MUST provide a Service Provider resource
Creation Factories MUST OSLC service providers MUST provide creation factories to enable resource creation via HTTP POST
Query Capabilities MUST OSLC service providers MUST provide query capabilities to enable clients to query for resources
Query Syntax MUST OSLC query capabilities MUST support the OSLC Core Query Syntax and MAY use other query syntax
Delegated UI Dialogs MUST OSLC Services MUST offer delegated UI dialogs (creation and selections) specified via service provider resource
UI Preview SHOULD OSLC Services SHOULD offer UI previews for resources that may be referenced by other resources
HTTP Basic Authentication MAY OSLC Services MAY support Basic Auth and should do so only over HTTPS
OAuth Authentication SHOULD OSLC Services SHOULD support OAuth and can indicate the required OAuth URLs via the service provider resource
Error Responses MAY OSLC Services MAY provide error responses using Core defined error formats
RDF/XML Representations MUST OSLC services MUST provide an RDF/XML representation for HTTP GET requests and MUST support RDF/XML representations on POST and PUT requests.
XML Representations MAY OSLC services MAY provide a XML representation for HTTP GET, POST and PUT requests that conform to the Core Guidelines for XML.
JSON Representations SHOULD OSLC services SHOULD provide JSON representations for HTTP GET, POST and PUT requests that conform to the Core Guidelines for JSON
HTML Representations SHOULD OSLC services SHOULD provide HTML representations for HTTP GET requests

Specification Versioning

See OSLC Core Specification Versioning section.

Service providers that support the resource formats and services in this specification MUST use HTTP response header of OSLC-Core-Version with a value of 2.0 and OSLC-Asset-Version with a value of 2.0. Consumers MAY request formats and services defined in this document by providing a HTTP request header of OSLC-Core-Version with a value of 2.0. See section below on Version Compatibility with OSLC Asset 1.0 Specifications.

Namespaces

In addition to the namespace URIs and namespace prefixes oslc, rdf, dcterms and foaf defined in the OSLC Core specification, OSLC Asset Management defines the namespace URI of http://open-services.net/ns/asset# with a namespace prefix of oslc_asset

Resource Formats

In addition to the requirements for OSLC Core Resource Formats section, this section outlines further refinements and restrictions.

For HTTP GET requests on all OSLC Asset Management and OSLC Core defined resource types,

  • Asset Management Providers MUST provide RDF/XML representations, SHOULD provide JSON representations, and MAY provide XML representations. The XML and JSON representations SHOULD follow the guidelines outlined in the OSLC Core Representations Guidance.
  • Asset Management Consumers requesting RDF/XML SHOULD be prepared for any valid RDF/XML document. Asset Management Consumers requesting XML or JSON SHOULD be prepared for representations that follow the guidelines outlined in the OSLC Core Representations Guidance.
  • Asset Management Providers SHOULD support an [X]HTML representation and a user interface (UI) preview as defined by UI Preview Guidance

For HTTP PUT/POST request formats for resource type of Asset:

  • Asset Management Providers MUST accept RDF/XML representations, SHOULD accept JSON representations, and MAY accept XML representations. Asset Management Providers accepting RDF/XML SHOULD be prepared for any valid RDF/XML document. For XML or JSON, Asset Management Providers SHOULD be prepared for representations that follow the guidelines outlined in the OSLC Core Representations Guidance.

For HTTP GET response formats for Query requests,

Asset Management Providers MUST provide RDF/XML representations, SHOULD provide JSON and Atom Syndication Format XML representations, and MAY provide XML representations.

When Asset Management Consumers request:

  • application/rdf+xml Asset Management Providers MUST respond with RDF/XML representation without restrictions.
  • application/json Asset Management Providers SHOULD respond with JSON representation as defined in the OSLC Core Representations Guidance.
  • application/xml Asset Management Provider MAY respond with OSLC-defined abbreviated XML representation as defined in the OSLC Core Representations Guidance
  • application/atom+xml Asset Management Provider SHOULD respond with Atom Syndication Format XML representation as defined in the OSLC Core Representations Guidance
  • The Atom Syndication Format XML representation SHOULD use RDF/XML representation without restrictions for the atom:content entries representing the resource representations.

See Query Capabilities for additional information when Resource Shapes affect representation.

Content Negotiation

OSLC Core Guidance clearly points to RDF representations (and specifically RDF/XML) as a convention that all OSLC Provider implementations minimally provide and accept. OSLC Asset Provider implementations are strongly encouraged to adopt this convention. Future versions of this specification are expected to require RDF representations for all operations and relax requirements for specialized XML representations.

XML Representation - identified by the application/xml content type. Format representation rules are outlined in Core OSLC Core Resource Formats section

RDF/XML Representation - identified by the application/rdf+xml content type. No additional guidance is given. The OSLC Core describes an algorithm for generating consistent formats that are used as examples only.

JSON Representation - identified by the application/json content type. Format representation rules are outlined in Core OSLC Core Resource Formats section.

Atom Syndication Format XML Representation - identified by the application/atom+xml content type. Format representation rules are outlined in Core OSLC Core Resource Formats section.

Authentication

See OSLC Core Authentication section. Asset Management puts no additional constraints on authentication.

Error Responses

See OSLC Core Error Responses section. Asset Management puts no additional constraints on error responses.

Pagination

OSLC Asset service providers SHOULD support pagination of query results and MAY support pagination of a single resource’s properties as defined by the OSLC Core Specification.

Requesting and Updating Properties

Requesting a Subset of Properties

A client MAY request a subset of a resource’s properties as well as properties from a referenced resource. In order to support this behavior a service provider MUST support the oslc.properties and oslc.prefix URL parameter on a HTTP GET request on individual resource request or a collection of resources by query. If the oslc.properties parameter is omitted on the request, then all resource properties MUST be provided in the response.

Updating a Subset of Properties

A 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.

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.

Labels for Relationships

Asset relationships to other resources are represented as properties whose values are the URI of the object or target resource. When an Asset relationship property is to be presented in a user interface, it may be helpful to provide an informative and useful textual label for that relationship instance. (This in addition to the relationship property URI and the object resource URI, which are also candidates for presentation to a user.) To this end, OSLC providers MAY support a dcterms:title link property in Asset resource representations, using the anchor approach outlined in the OSLC Core Links Guidance. In addition to the textual label, the Asset resource definition defines several properties that can be used to describe the relationship from one Asset resource to another Asset resource.

RDF/XML and XML example using reified statement:

<rdf:RDF 
     xmlns:dcterms="http://purl.org/dc/terms/" 
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:oslc_asset="http://open-services.net/ns/asset#">

    <oslc_asset:Asset rdf:about="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0">
         <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
    </oslc_asset:Asset>

    <rdf:Description rdf:about="#relationship1">
        <dcterms:title>Build Configuration</dcterms:title>
   </rdf:Description>
</rdf:RDF>

Custom Properties

Asset management providers SHOULD allow consumers to define custom properties. If providers allow consumers to define custom properties, they MUST allow the consumer to optionally specify an HTTP URI for that data element, and the specified URI MUST be used in the RDF representation of all resources that contain the data element. The specified URI MAY be part of an industry standard such as DC, FOAF, or OSLC, or it MAY be defined by the user’s organization. If the URI is defined by the user’s organization, then they SHOULD make it dereferencable as per the W3C Best Practices for Publishing RDF Vocabularies.

If the user does not specify the optional URI, then the provider MUST use a default generated HTTP URI. The generated URI SHOULD be as human-readable as possible. One method for achieving human-readability is to apply a human-friendly name mangling algorithm to the user-defined label for the data element. The tool SHOULD make the generated URI dereferencable as per the W3C Best Practices for Publishing RDF Vocabularies. The published RDF vocabulary SHOULD include any relevant descriptive information provided the user as part of the data element definition, e.g. the label and description.

OSLC Asset Management Resource Definitions

Asset

An Asset is anything tangible or intangible that is capable of being owned or controlled to produce value, and is held to have positive economic value. This includes not only software products, but also buildings, servers, automobiles, pumps, oil wells, etc. These properties include such things as name, description, classification, and the Artifact properties of an Asset.

The Asset resource properties are not limited to the ones defined in this specification, service providers 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.

Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Core: Common Properties
dcterms:identifier zero-or-one True String n/a n/a A unique identifier for a resource. Assigned by the service provider when a resource is created.
dcterms:title exactly-one unspecified XMLLiteral n/a n/a Short name identifying a resource, often used as an abbreviated identifier for presentation to end-users. SHOULD include only content that is valid inside an XHTML element.
dcterms:description zero-or-one unspecified XMLLiteral n/a n/a Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML element.
dcterms:creator zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case
dcterms:contributor zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any The person(s) who are responsible for this asset. (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp latest resource modification (reference: Dublin Core).
rdf:type zero-or-many unspecified Resource Reference n/a The resource type URIs. One reference should have the value of http://open-services.net/ns/asset#Asset.
oslc:serviceProvider zero-or-many unspecified Resource Reference oslc:ServiceProvider The scope of a resource is a URI for the resource’s OSLC Service Provider.
oslc:instanceShape zero-or-one unspecified Resource Reference oslc:ResourceShape Resource Shape that provides hints as to resource property value-types and allowed values.
Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Asset: Start of additional properties
oslc_asset:guid zero-or-one unspecified String n/a n/a An identifier for the asset. Assigned by the service provider when a resource is created. Different versions of the same asset will share the same identifier.
oslc_asset:version zero-or-one unspecified String n/a n/a The version of the asset. Possible values may include ‘1.0’, ‘2.0’, etc.
dcterms:abstract zero-or-one unspecified XMLLiteral n/a n/a Short description (reference: Dublin Core) or often a single line summary of the resource
dcterms:type zero-or-one unspecified Resource Reference n/a The type of the asset based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:state zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any Used to indicate the state of the asset based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:categorization zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any A categorization to classify an asset. The category schema values are defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
oslc_asset:manufacturer zero-or-one unspecified String n/a n/a The name of the asset manufacturer.
oslc_asset:model zero-or-one unspecified String n/a n/a The value of the asset model.
oslc_asset:serialNumber zero-or-one unspecified String n/a n/a The serial number assigned by the asset manufacturer.
oslc_asset:tag zero-or-many unspecified String n/a n/a Specifies the asset tag value for an Asset. Asset tags are typically human readable labels. For hardware assets, these tags are durable, securely attached to equipment, and may also be readable by barcode and/or RFID.
oslc_asset:artifact zero-or-many unspecified Local Resource Inline oslc_asset:Artifact An Artifact fragment contained in this Asset resource.
oslc_asset:artifactFactory exactly-one unspecified Resource Reference any Resource URI used to post new artifacts to the asset.
Prefixed Name Occurs Read-only Value-type Representation Range Description
Relationship Properties: This grouping of properties are used to identify relationships between resources managed by the current or other OSLC Service Providers
dcterms:relation zero-or-many False Resource Reference any This relationship is loosely coupled and has no specific meaning. Details about this relationship may be included in a reified statement.
Prefixed Name Occurs Read-only Value-type Representation Range Description
Related Resource Reified Statement Properties: This grouping of properties is used to provide additional details about a relationship in a reified statement
oslc_asset:relationshipType zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any The type of this relationship from the perspective of the dcterms:relation resource based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.
dcterms:creator zero-or-many unspecified Either Resource or Local Resource Either Reference or Inline any Creator or creators of the relationship (reference: Dublin Core). It is likely that the target resource will be a foaf:Person but that is not necessarily the case.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of the relationship creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp of the latest relationship modification (reference: Dublin Core).
oslc_asset:state zero-or-one unspecified Either Resource or Local Resource Either Reference or Inline any Used to indicate the state of the relationship based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.

Artifact

An Artifact is a fragment within an asset resource that describes an Artifact Media Resource. An artifact fragment may only be updated though an Asset resource and it is not possible to perform operations directly on the Artifact fragment

The Artifact fragment properties are not limited to the ones defined in this specification, service providers 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.

Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Artifact Fragment: The grouping of properties that define an artifact
rdf:type zero-or-many unspecified Resource Reference n/a The resource type URIs. One reference should have the value of http://open-services.net/ns/asset#Artifact.
dcterms:title exactly-one unspecified XMLLiteral n/a n/a The name of the artifact. Title (reference: Dublin Core) of the resource represented in text XHTML content. SHOULD include only content that is valid inside an XHTML element.
oslc:label zero-or-one unspecified XMLLiteral n/a n/a The label of the artifact. Subject (reference: Dublin Core) an abbreviated presentation for the end-users. SHOULD include only content that is valid inside an XHTML element.
oslc_asset:content exactly-one unspecified Resource Reference Artifact Media The media resource reference URI (the artifact bytes).
dcterms:format zero-or-one unspecified String n/a n/a The mime type of the artifact media resource.
oslc_asset:size zero-or-one True Integer n/a n/a The size of the artifact media resource in bytes.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core).
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp last latest resource modification (reference: Dublin Core).

Artifact Media

The artifact media represents the actual content of an artifact. The URI for the artifact media resource is defined by the oslc_asset:content property of an artifact fragment within an asset resource.

A client may publish a new artifact to an asset making a POST request to the asset’s artifact factory URI as defined by the oslc_asset:artifactFactory property of the asset resource. The request MUST contain an oslc_asset.name header indicating the path and name of the new artifact and the body of the POST MUST contain the contents of the artifact. A successful response from the provider MUST return a status code of 201 and a Location Header indicating the URI of the Media Resource. In addition, the provider MUST add a new artifact fragment to the asset and fill in the mandatory properties including size, and creation time. The client may later update the non-read only properties of this fragment.

See the Publish an artifact sample for additional details.

Providers MUST also support URI artifacts. URI artifacts do not contain content, but instead the oslc_asset:content property’s value is a URI external to the asset. To create a URI artifact, clients POST an artifact resource to the artifact factory URI. The request MUST contain an oslc_asset.name header indicating the path and name of the new artifact URI. A successful response from the provider MUST return a status code of 201 and a Location Header indicating the URI of the artifact URI. In addition, the provider MUST add a new artifact fragment to the asset and fill in the mandatory properties such as creation time. The client may later update the non-read only properties of this fragment.

See the Publish a URI artifact sample for additional details.

Asset Management Service Provider Capabilities

Service Discovery and Description

OSLC Asset Management service providers MUST provide a Service Provider Resource that can be retrieved at a implementation dependent URI.

OSLC Asset Management service providers MAY provide a Service Provider Catalog Resource that can be retrieved at a implementation dependent URI.

OSLC Asset Management service providers MUST provide a oslc:serviceProvider property for their defined resources that will be the URI to a Service Provider Resource.

OSLC Asset Management service providers MUST supply a value of http://open-services.net/ns/asset# for the property oslc:domain on either oslc:Service or oslc:ServiceProviderCatalog resources.

Creation Factories

OSLC Asset Management service providers MUST support Creation Factories and list them in the Service Provider Resource as defined by OSLC Core. OSLC Asset Management service providers SHOULD support Resource Shapes for Creation Factories as defined in OSLC Core Specification

Query Capabilities

OSLC Asset Management service providers MUST support the Query Capabilities as defined by OSLC Core. OSLC Asset Management service providers SHOULD support Resource Shapes for Query Capability as defined in OSLC Core Specification

The Query Capability MUST support these parameters:

  • oslc.where
  • oslc.select
  • oslc.properties
  • oslc.prefix

If shape information is NOT present with the Query Capability, service providers SHOULD use these default properties to contain the result:

Delegated User Interface Dialogs

OSLC Asset Management service providers SHOULD support the selection of resources by delegated web-based user interface dialogs Delegated UIs as defined by OSLC Core.

OSLC Asset Management service providers MAY support the creation of resources by delegated web-based user interface dialogs Delegated UIs as defined by OSLC Core.

OSLC Asset Management service providers MAY support the pre-filling of creation dialogs based on the definition at Delegated UIs.

The service providers supports the delegated UIs as follows:

Asset Management Resource Selection Creation
Asset SHOULD MAY

Version Compatibility with 1.0 Specifications

The goal is to provide a smooth transition to 2.0 for both Consumers and Providers. This section will clarify the usage of 1.0 media types so that Providers can support both 1.0 and 2.0 Consumers when HTTP requests are made for a resource with the same URI.

Media Types

For an Asset Resource format identification of RDF/XML and XML, the media type used for this representation SHOULD be application/rdf+xml or application/xml.

For an Asset Resource format identification of JSON, the media type used for this representation SHOULD be application/json.

Appendix A: Samples

(this section is informative)

See [[OSLC Asset Management 2.0 Samples]].

Appendix B: Resource Shapes

(this section is informative)

See [[OSLC Asset Management 2.0 Appendix B: Resource Shapes]]

Appendix C: Notices and References

Contributors

  • Brad Sandler (IBM)
  • Dave Johnson (IBM)
  • Edwin Freekenhorst (Shell)
  • Eric Bordeau (IBM)
  • Gili Mendel (IBM; OSLC Asset Management Lead)
  • Grant Larsen (IBM)
  • Hari Padmanabhan (IBM)
  • Jaimin Patel (WebLayers)
  • John Favazza (WebLayers)
  • Kevin Bauer (IBM)
  • Randy Lexvold (the Emphasys Group)
  • Ren Renganathan (Citigroup)
  • Scott Bosworth (IBM)
  • Sheehan Anderson (IBM)
  • Srimanth Gunturi (IBM)

Reporting Issues on the Specification

The working group participants who author and maintain this working draft specification, monitor a distribution list where issues or questions can be raised, see Asset Management Mailing List

Also the issues found with this specification and their resolution can be found at [[OSLC Asset Management 2.0 specification issues]].

Intellectual Property Covenant

The members of the Working Group (or as appropriate, their employers) have documented a Patent Non-Assertion Covenant for implementations of the Asset Management 2.0 Specification, as described in the open-services.net Terms of Use. Details of the Covenant may be found here.

References

]]> Mon, 27 Aug 2012 16:19 EDT <![CDATA[OSLC Asset Management 2.0 specification issues]]> OSLC Administrator http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-specification-issues/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-specification-issues/#When:1346091716 This section captures the issues raised via review comments on the [[OSLC Asset Management 2.0 Specification]]

Issues are organized via the spec outline.

Here’s what the states mean:

  • OPEN - indicates that we have no response for the issue yet
  • RESOLVED - indicates that we have a response that we believe resolves the issue
    • RESOLVED - indicates it is resolved as by above definition and edits in the draft specification have been made.
  • CLOSED - issue has been resolved and the resolution has been reviewed by the workgroup
  • DEFERRED - indicates that issue will be addressed in guidance after the specification converges
  • TABLED - indicates that issue will be reconsidered at some later but unspecified date

After Finalization of 2.0

During Convergence and Finalization of 2.0

  1. CLOSED The related asset reified statement properties that describe the relationship should start with the term ‘relationship’. This allows implementations to optionally include properties of the related asset in the reified statement that may otherwise conflict with existing properties. For example, the property to describe the creator of the relationship should be changed from ‘dcterms:creator’ to ‘dcterms:relationshipCreator’. This allows an implementation to use ‘dcterms:creator’ to describe the creator of the related asset. (SheehanAnderson, 11 October 2011)
    • Response The property names will not be changed. We will not encourage implementations to include information about the related resource in the reified statement. (SheehanAnderson 11 October 2011)
  2. CLOSED The Compliance table and the Resource Formats section seem to contradict each other on a) the MUST (Compliance) /SHOULD (Resource Formats) status of JSON b the SHOULD (Compliance) and MUST (Resource Formats) status of RDF/XML on a POST request. (MichaelFiedler, 11 October 2011)
    • Response Updated the Compliance and Resource Format sections of the specification. (SheehanAnderson 11 October 2011)
  3. CLOSED The specification does not talk about the DELETE HTTP method for resources. Since we do internally support DELETE in RAM it would be better to take a stance on it. Workitem OSLC v2 Specification should discuss about DELETE resources has been opened for this. Alternatively is there any necessity for HEAD and OPTIONS methods? (SrimanthGunturi, 20 October 2011)
    • Response The DELETE HTTP method for resources is defined in the core specification. See Resource Operations. The asset specification also mentions that implementations MUST support the resource operations as defined in the core specification. See Asset Management Compliance. (SheehanAnderson 24 October 2011)
  4. CLOSED The specification contains both an rdf:type and dcterms:type property. To reduce confusion these two properties should be combined into a single rdf:type property and the the dcterms:type property should not be used. Other specifications (including CM) plan to take this same approach. (SheehanAnderson, 13 December 2011)
    • Response The specification now includes two rdf:type properties, one to represent the resource type and a second to represent the asset type. However, we have discovered that Jena has issues serializing/deserializing resources with multiple rdf:type properties. See issue 14. (SheehanAnderson 03 January 2012)
  5. CLOSED Currently the dcterms:type, oslc_asset:state, and oslc_categorization properties state that their representations can be a String or Resource. Having two potential representations for a single property will pose issues for consumers attempting to parse an asset resource. The properties should instead either be a String or Resource. We think it makes the most sense at this time to define the properties as a resource (SheehanAnderson, 13 December 2011)
    • Response The dcterms:type, oslc_asset:state, and oslc_categorization properties have been updated to resources in the specifications. The actual resources for these properties are not defined by the specification. (SheehanAnderson 03 January 2012)
  6. CLOSED Upon implementing ServiceProviderCatalog service, there was no data to fill in the oslc:details predicate of oslc:ServiceProvider. The example of ServiceProviderCatalog should be cleaned up. (SrimanthGunturi, 14 December 2011)
    • Response The oslc:details property is not required by core (occurs zero-or-many) so it has been removed from the examples. (SheehanAnderson 03 January 2012)
  7. CLOSED oslc:creationDialog example has this predicate dcterms:description which is not specified in the OSLC Core specification.(SrimanthGunturi, 14 December 2011)
    • Response Removed dcterms:description property from example. (SheehanAnderson 03 January 2012)
  8. CLOSED In implementing oslc_asset:Asset, wanted to discuss if we really need the dcterms:creator predicate? We dont use it that much in RAM itself. If there are no good usecases, I would vote to remove it. (SrimanthGunturi, 14 December 2011)
    • Response The property is listed in the specification with an occurs of zero-or-many. It’s not necessary for providers to include the property. It will be left in the specification to be consistent with other OSLC specifications which generally include this property for resources. (SheehanAnderson 03 January 2012)
  9. CLOSED oslc_asset:Asset has the predicate oslc:instanceShape. Why dont we use oslc:resourceShape? (SrimanthGunturi, 14 December 2011)
    • Response oslc:instanceShape should be used as it is more specific and assets of different types may have different instance shapes. (SheehanAnderson 03 January 2012)
  10. CLOSED oslc_asset:Asset has two predicates which have types - oslc_asset:Artifact and oslc_asset:ArtifactFactory. Both of these should be links to the appropriate definitions. (SrimanthGunturi, 14 December 2011)
    • Response The range for oslc_asset:ArtifactFactory has been changed to ‘any’. The oslc_asset:Artifact range can not be linked to the correct portion of the table due to limitations in the wiki, but the definition for an artifact is directly below this property. (SheehanAnderson 03 January 2012)
  11. CLOSED oslc_asset:Asset has predicate oslc_asset:ArtifactFactory. Its type is oslc_asset:AssetFactory. We should probably change it to oslc_asset:ArtifactFactory. (SrimanthGunturi, 14 December 2011)
    • Response Changed oslc_asset:ArtifactFactory range to ‘any’. (SheehanAnderson 03 January 2012)
  12. CLOSED I could not find the resource definition for oslc_asset:ArtifactFactory. (SrimanthGunturi, 14 December 2011)
    • Response Changed oslc_asset:ArtifactFactory range to ‘any’. (SheehanAnderson 03 January 2012)
  13. CLOSED Asset resource’s oslc:instanceShape predicate should have the asset-type or the Asset shape? Sample needs to be updated based on this. (SrimanthGunturi, 23 December 2011)
    • Response We determined that the example is correct. The URL should point to a shape, not the asset type. It is possible that the instance shape is based on the asset type, but this is not necessarily the case. (SheehanAnderson 03 January 2012)
  14. CLOSED For issue #4 we decided to have two rdf:type predicates for Asset resource. In example we only need to show the asset-type rdf:type as the Asset’s rdf:type is implicit in <oslc_asset:Asset/> element’s name.(SrimanthGunturi, 23 December 2011)
    • Response Consumers should be able to handle multiple rdf:type properties. Implementations should return an rdf representation for resources and not use abbreviated XML. (SheehanAnderson 03 January 2012)
  15. CLOSED The asset resource currently uses dcterms:title to represent an asset’s name, dcterms:abstract to represent an asset’s short description, and dcterms:description to represent an asset’s full description. Some members have raised concerns as to whether these are the right property names for their values and if dcterms:abstract and dcterms:description are potentially reversed. This needs to be investigated. (SheehanAnderson, 03 January 2012)
    • Response We looked over the Dublin Core documentation and determined that dcterms:abstract should match to the short description and dcterms:description should map to the full asset description. (SheehanAnderson 03 January 2012)
  16. CLOSED - OSLC Core specification for ResourceShape resource says the literal value type for XMLLiteral is “http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral” . However the Asset resource shape sample uses "http://www.w3.org/2001/XMLSchema#XMLLiteral" in some places. (SrimanthGunturi, 29 February 2012)
    • Response Updated resource [[OSLC Asset Management 2.0 Appendix B: Resource Shapes]] to fix error. (SheehanAnderson 12 March 2012)
  17. CLOSED - Asset ResourceShape sample has oslc:range predicate value with protocol defined twice - <oslc:range rdf:resource=”http://http://xmlns.com/foaf/0.1/Person” />. (SrimanthGunturi, 29 February 2012)
    • Response Updated resource [[OSLC Asset Management 2.0 Appendix B: Resource Shapes]] to fix error. (SheehanAnderson 13 March 2012)
  18. CLOSED - Asset ResourceShape sample has dcterms:identifier pedicate using the wrong URL - <oslc:propertyDefinition rdf:resource=”http://open-services.net/ns/asset#identifier” />. (SrimanthGunturi, 1 March 2012)
    • Response Updated resource [[OSLC Asset Management 2.0 Appendix B: Resource Shapes]] to fix error. (SheehanAnderson 12 March 2012)
]]> Mon, 27 Aug 2012 14:21 EDT <![CDATA[OSLC Asset Management 2.0 Samples]]> OSLC Administrator http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Samples/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Samples/#When:1346089353 [TOC]

Overview

This is a collection of various Asset Management resources in a variety of formats to better illustrate their usage. These are samples only and not intended to show every permutation of the various formats.

Service Provider Samples

ServiceProviderCatalog as RDF/XML

The build system starts with a URL to the asset management service catalog which it will use to discover the asset management services.

Request

GET http://example.com/assets/cat
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/rdf+xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:oslc="http://open-services.net/ns/core#" 
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
   <oslc:ServiceProviderCatalog rdf:about="http://example.com/assets/cat">
      <dcterms:title>Product Grouping</dcterms:title>
      <dcterms:description>Lists various asset management systems by Product Grouping</dcterms:description>
      <oslc:domain rdf:resource="http://open-services.net/ns/asset#" />
      <dcterms:publisher>
         <oslc:Publisher>
            <dcterms:title>OSLC Asset Management Working Group</dcterms:title>
            <dcterms:identifier>com.example.oslc.asset</dcterms:identifier>
            <oslc:icon rdf:resource="http://example.com/icons/assets.ico" />
         </oslc:Publisher>
      </dcterms:publisher>
      <oslc:serviceProvider>
         <oslc:ServiceProvider rdf:about="http://example.com/assets/sp/f">
            <dcterms:title>France region</dcterms:title>
         </oslc:ServiceProvider>
      </oslc:serviceProvider>
      <oslc:serviceProvider>
         <oslc:ServiceProvider rdf:about="http://example.com/assets/sp/b">
            <dcterms:title>Brazil region</dcterms:title>
         </oslc:ServiceProvider>
      </oslc:serviceProvider>
      <oslc:serviceProviderCatalog>
         <oslc:ServiceProviderCatalog rdf:about="http://example.com/assets/cat2">
            <dcterms:title>Product Grouping - [Asia/Pacific](Asia/Pacific.html)</dcterms:title>
            <dcterms:publisher>
               <oslc:Publisher>
                  <dcterms:title>OSLC Asset Management Working Group</dcterms:title>
                  <dcterms:identifier>com.example.oslc.asset</dcterms:identifier>
                  <oslc:icon rdf:resource="http://example.com/icons/assets.ico" />
               </oslc:Publisher>
            </dcterms:publisher>
            <oslc:serviceProvider>
               <oslc:ServiceProvider rdf:about="http://example.com/sp/a">
                  <dcterms:title>China region</dcterms:title>
               </oslc:ServiceProvider>
            </oslc:serviceProvider>
         </oslc:ServiceProviderCatalog>
      </oslc:serviceProviderCatalog>
      <oslc:oauthConfiguration>
         <oslc:OAuthConfiguration>
            <oslc:oauthRequestTokenURI rdf:resource="http://example.com/assets/oauth-request-token" />
            <oslc:authorizationURI rdf:resource="http://example.com/assets/oauth-authorization" />
            <oslc:oauthAccessTokenURI rdf:resource="http://example.com/assets/oauth-access-token" />
         </oslc:OAuthConfiguration>
      </oslc:oauthConfiguration>
   </oslc:ServiceProviderCatalog>
</rdf:RDF>

ServiceProvider as RDF/XML

From the services catalog the build system locates the Service Provider it is interested in /assets/sp/b and gets that provider.

Request

GET http://www.example.com/assets/sp/b
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/" xmlns:oslc="http://open-services.net/ns/core#"
   xml:lang="en">
   <oslc:ServiceProvider rdf:about="http://example.com/assets/sp/b">
      <dcterms:title>Brazil region assets</dcterms:title>
      <dcterms:description>Example OSLC Asset Management Service</dcterms:description>
      <dcterms:publisher>
         <oslc:Publisher>
            <dcterms:title>OSLC Asset Management Working Group</dcterms:title>
            <dcterms:identifier>com.example.oslc.asset</dcterms:identifier>
            <oslc:icon rdf:resource="http://example.com/icons/assets.ico" />
         </oslc:Publisher>
      </dcterms:publisher>
      <oslc:prefixDefinition>
         <oslc:PrefixDefinition>
            <oslc:prefix>rdf</oslc:prefix>
            <oslc:prefixBase rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#" />
         </oslc:PrefixDefinition>
      </oslc:prefixDefinition>
      <oslc:prefixDefinition>
         <oslc:PrefixDefinition>
            <oslc:prefix>dcterms</oslc:prefix>
            <oslc:prefixBase rdf:resource="http://purl.org/dc/terms/" />
         </oslc:PrefixDefinition>
      </oslc:prefixDefinition>
      <oslc:prefixDefinition>
         <oslc:PrefixDefinition>
            <oslc:prefix>oslc</oslc:prefix>
            <oslc:prefixBase rdf:resource="http://open-services.net/ns/core#" />
         </oslc:PrefixDefinition>
      </oslc:prefixDefinition>
      <oslc:prefixDefinition>
         <oslc:PrefixDefinition>
            <oslc:prefix>oslc_asset</oslc:prefix>
            <oslc:prefixBase rdf:resource="http://open-services.net/ns/asset#" />
         </oslc:PrefixDefinition>
      </oslc:prefixDefinition>
      <oslc:service>
         <oslc:Service>
            <oslc:domain rdf:resource="http://open-services.net/ns/asset#" />
            <oslc:creationFactory>
               <oslc:CreationFactory>
                  <dcterms:title>Default Asset Management factory</dcterms:title>
                  <oslc:label>Asset</oslc:label>
                  <oslc:creation rdf:resource="http://example.com/bugs/factory" />
                  <oslc:resourceShape rdf:resource="http://example.com/shapes/assets" />
                  <oslc:resourceType rdf:resource="http://open-services.net/ns/asset#Asset" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/core#default" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/asset#defect" />
               </oslc:CreationFactory>
            </oslc:creationFactory>
       <oslc:queryCapability>
                        <oslc:QueryCapability>
                              <dcterms:title>Asset Query</dcterms:title>
                              <oslc:label>assetquery</oslc:label>
                              <oslc:queryBase rdf:resource="http://example.com/query" />
                              <oslc:resourceShape rdf:resource="http://example.com/shapes/asset" />
                           </oslc:QueryCapability>
                        </oslc:queryCapability>
            <oslc:creationDialog>
               <oslc:Dialog>
                  <dcterms:title>New Asset</dcterms:title>
                  <oslc:label>Asset</oslc:label>
                  <oslc:dialog rdf:resource="http://example.com/assets/dialogs/newasset" />
                  <oslc:hintWidth>651px</oslc:hintWidth>
                  <oslc:hintHeight>294px</oslc:hintHeight>
                  <oslc:resourceType rdf:resource="http://open-services.net/ns/asset#Asset" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/core#default" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/asset#Asset" />
               </oslc:Dialog>
            </oslc:creationDialog>
            <oslc:selectionDialog>
               <oslc:Dialog>
                  <dcterms:title>Pick Asset</dcterms:title>
                  <oslc:label>Asset</oslc:label>
                  <oslc:dialog rdf:resource="http://example.com/assets/dialogs/pickasset" />
                  <oslc:hintWidth>500px</oslc:hintWidth>
                  <oslc:hintHeight>250px</oslc:hintHeight>
                  <oslc:resourceType rdf:resource="http://open-services.net/ns/asset#Asset" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/core#default" />
                  <oslc:usage rdf:resource="http://open-services.net/ns/asset#Asset" />
               </oslc:Dialog>
            </oslc:selectionDialog>
         </oslc:Service>
      </oslc:service>
   </oslc:ServiceProvider>
</rdf:RDF>

Retrieve Samples

Retrieve an asset as RDF/XML

Request

GET   <http://example.com/oslc/assets/4667/1.0>
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/" 
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">
   <oslc_asset:Asset rdf:about="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0">
      <rdf:type rdf:resource="http://open-services.net/ns/asset#Asset"/>
      <dcterms:title>Build Configuration for Myco Services</dcterms:title>
      <oslc_asset:guid>CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA</oslc_asset:guid>
      <oslc_asset:version>1.0</oslc_asset:version>
      <oslc:instanceShape rdf:resource="http://example.com/shapes/Build Configuration"/>
      <dcterms:abstract>Build Configuration Myco's web services application</dcterms:abstract>
      <dcterms:creator rdf:resource="http://example.com/users/joe"/>
      <dcterms:contributor rdf:resource="http://example.com/users/bob"/>
      <dcterms:modified>2011-09-16T08:42:11.265Z</dcterms:modified>
      <dcterms:created>2011-07-04T11:00:00.000Z</dcterms:created>
      <dcterms:type rdf:resource="http://example.com/types/buildConfiguration"/>
      <oslc_asset:state rdf:resource="http://example.com/states/Approved"/>
      <oslc_asset:categorization rdf:resource="http://example.com/categories/Build/Frequency/Daily"/>
      <oslc_asset:artifactContentFactory rdf:resource="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0/artifacts"/>
      <oslc_asset:artifact rdf:resource="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0#artifacts/build.xml"/>
      <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
   </oslc_asset:Asset>
   <rdf:Description rdf:about="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0#artifacts/build.xml">       
      <rdf:type rdf:resource="http://open-services.net/ns/asset#Artifact"/>
      <dcterms:title>build.xml</dcterms:title>
      <dcterms:label>Build Start File</dcterms:label>
      <oslc_asset:content rdf:resource="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0/artifactContents/build.xml"/>
      <dcterms:format>text/xml</dcterms:format>
      <oslc_asset:size>10240</oslc_asset:size>
      <dcterms:modified>2011-08-12T14:32:27.123Z</dcterms:modified>
      <dcterms:created>2011-06-12T14:32:27.123Z</dcterms:created>
   </rdf:Description>
   <rdf:Description rdf:about="#relationship1">       
      <oslc_asset:relationshipType rdf:resource="http://example.com/oslc/relationships/Dependency/"/>
      <dcterms:creator rdf:resource="http://example.com/users/joe" />
      <oslc_asset:state rdf:resource="http://example.com/states/Approved"/>
      <dcterms:modified>2011-05-02T07:00:00.123Z</dcterms:modified>
      <dcterms:created>2011-04-28T10:00:00.000Z</dcterms:created>
   </rdf:Description>
</rdf:RDF>

Download an asset as a zip file

Request

GET http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0
Accept: application/zip
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/zip
ETag: xxx
Content-Length: nnn

Body: Zipped content of the asset

Publish Samples

Publish an asset as RDF/XML

Create a new asset with a relationship to an existing asset.

Request

POST <http://example.com/oslc/assets>
Accept: application/rdf+xml
Content-Type: application/rdf+xml
OSLC-Core-Version: 2.0
Body:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/" 
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">
   <oslc_asset:Asset>
      <rdf:type rdf:resource="http://open-services.net/ns/asset#Asset"/>
      <dcterms:type rdf:resource="http://example.com/types/Implementation"/>
      <dcterms:title>Services Implementation</dcterms:title>
      <oslc_asset:version>1.0</oslc_asset:version>
      <dcterms:abstract>Build Configuration Myco's web services application</dcterms:abstract>
      <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
   </oslc_asset:Asset>
   <rdf:Description rdf:about="#relationship1">       
      <oslc_asset:relationshipType rdf:resource="http://example.com/relationships/Dependency/"/>
   </rdf:Description>
</rdf:RDF>

Response

HTTP/1.0 201 Created
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn
Location: <http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0>

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/" 
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">
   <oslc_asset:Asset rdf:about="http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0">
      <rdf:type rdf:resource="http://open-services.net/ns/asset#Asset"/>
      <dcterms:type rdf:resource="http://example.com/types/Implementation"/>
      <dcterms:title>Services Implementation</dcterms:title>
      <oslc_asset:guid>B538BDD4-53CB-D52C-0E26-5997025FE8C3</oslc_asset:guid>
      <oslc_asset:version>1.0</oslc_asset:version>
      <dcterms:abstract>Build Configuration Myco's web services application</dcterms:abstract>
      <dcterms:creator rdf:resource="http://example.com/oslc/users/joe"/>
      <dcterms:modified>2011-09-16T08:42:11.265Z</dcterms:modified>
      <dcterms:created>2011-09-16T08:42:11.265Z</dcterms:created>
      <oslc_asset:state rdf:resource="http://example.com/states/Draft"/>
      <oslc_asset:artifactContentFactory rdf:resource="http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0/artifacts"/>
      <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
   </oslc_asset:Asset>
   <rdf:Description rdf:about="#relationship1">       
      <oslc_asset:relationshipType rdf:resource="http://example.com/relationships/Dependency/"/>
      <dcterms:creator rdf:resource="http://example.com/users/joe" />
      <oslc_asset:state rdf:resource="http://example.com/states/Draft"/>
      <dcterms:modified>2011-09-16T08:42:11.265Z</dcterms:modified>
      <dcterms:created>2011-09-16T08:42:11.265Z</dcterms:created>
   </rdf:Description>
</rdf:RDF>

Publish an artifact

Upload a new artifact to the asset that was published

Request

POST <http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0/artifacts>
oslc_asset.name: services.ear
Content-Type: application/java-archive
OSLC-Core-Version: 2.0

The POST body contains the content of the artifact.

Response

HTTP/1.0 201 Created
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn
Location: <http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0/artifacts/services.ear>

Publish a URI artifact

Upload a new URI artifact to the asset that was published

Request

POST <http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0/artifacts>
oslc_asset.name: /helpFolder/help
Content-Type: application/rdf+xml
OSLC-Core-Version: 2.0

Body: 
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/" 
   xmlns:oslc_asset="http://open-services.net/ns/artifact#">
   <oslc_asset:Artifact>    
      <rdf:type rdf:resource="http://open-services.net/ns/asset#Artifact"/>
      <dcterms:title>Build help documentation</dcterms:title>
      <dcterms:label>documentation</dcterms:label>
      <oslc_asset:content rdf:resource="http://help.example.com"/>
      <dcterms:format>text/html</dcterms:format>
   </oslc_asset:Artifact>
</rdf:RDF>

Response

HTTP/1.0 201 Created
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn
Location: <http://example.com/assets/B538BDD4-53CB-D52C-0E26-5997025FE8C3/1.0/artifacts/helpFolder/help>

Query Samples

Query result as RDF/XML

Query for all assets with ‘services’ in their title.

Request

GET http://example.com/query?oslc.where=dcterms:title="services"
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/rdf+xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF      
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">

     <oslc:ResponseInfo rdf:about="http://example.com/query?oslc.where=dcterms:title=&quot;services&quot;">
         <dcterms:title>Asset query service</dcterms:title>
     </oslc:ResponseInfo>

     <rdf:Description rdf:about="http://example.com/query">
        <rdfs:member rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
        <rdfs:member rdf:resource="http://example.com/assets/D6199D91-9662-6977-46EC-93E656CCB7B8/2.0"/>
        <rdfs:member rdf:resource="http://example.com/assets/83ECEEAA-6E38-D0A5-0739-22E4AF38A7EE/1.0"/>
     </rdf:Description>
</rdf:RDF>

Query result as RDF/XML with select

Query for all assets with ‘services’ in their title and are version ‘1.0’. Select the title of the asset and the title of the asset’s type.

Request

GET http://example.com/query?oslc.select=dcterms:title,dcterms:type{dcterms:title}&oslc;.where=dcterms:title="services" and oslc_asset:version="1.0"
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/rdf+xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF      
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">

     <oslc:ResponseInfo 
        rdf:about="http://example.com/query?oslc.select=dcterms:title,dcterms:type{dcterms:title}&amp;oslc.where=dcterms:title=&quot;services&quot; and oslc_asset:version=&quot;1.0&quot;">
        <dcterms:title>Asset query service</dcterms:title>
     </oslc:ResponseInfo>

     <rdf:Description rdf:about="http://example.com/query">
        <rdfs:member>
           <oslc_asset:Asset rdf:about="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0">
              <dcterms:title>Voice plan service</dcterms:title>
              <dcterms:type>
                 <dcterms:type rdf:about="http://example.com/types/Service">
                    <dcterms:title>Service</dcterms:title>
                 </dcterms:type>
              </dcterms:type>
           </oslc_asset:Asset>
        </rdfs:member>
        <rdfs:member>
           <oslc_asset:Asset rdf:about="http://example.com/assets/83ECEEAA-6E38-D0A5-0739-22E4AF38A7EE/1.0">
              <dcterms:title>Data plan service</dcterms:title>
              <dcterms:type>
                 <dcterms:type rdf:about="http://example.com/types/Service">
                    <dcterms:title>Service</dcterms:title>
                 </dcterms:type>
              </dcterms:type>
           </oslc_asset:Asset>
        </rdfs:member>
     </rdf:Description>
</rdf:RDF>

Query result for related assets as RDF/XML with select

Query for all assets related to asset http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0 and for each result select the asset name and relationship type title.

Request

GET http://example.com/query?oslc.select=dcterms:title,dcterms:relation{oslc_asset:relationshipType{dcterms:title}}&amp;oslc.where=dcterms:relation="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"
Accept: application/rdf+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 200 OK
OSLC-Core-Version: 2.0
Content-Type: application/rdf+xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF      
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_asset="http://open-services.net/ns/asset#">

     <oslc ResponseInfo rdf:about="http://example.com/query?oslc.select=dcterms:title,dcterms:relation{oslc_asset:relationshipType{dcterms:title}}&amp;oslc.where=dcterms:relati>
        <dcterms:title>Asset query service</dcterms:title>
     </oslc:ResponseInfo>

     <rdf:Description rdf:about="http://example.com/query">
        <rdfs:member>
           <oslc_asset:Asset rdf:about="http://example.com/assets/CDFE4153-9271-5CA6-425A-4CA6BE7BD7CA/1.0">
              <dcterms:title>Voice plan service</dcterms:title>
              <dcterms:relation rdf:ID="relationship1" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
           </oslc_asset:Asset>
        </rdfs:member>
        <rdfs:member>
           <oslc_asset:Asset rdf:about="http://example.com/assets/83ECEEAA-6E38-D0A5-0739-22E4AF38A7EE/1.0">
              <dcterms:title>Data plan service</dcterms:title>
              <dcterms:relation rdf:ID="relationship2" rdf:resource="http://example.com/assets/52C4702C-7CA2-E46E-D373-620482ECBEED/1.0"/>
           </oslc_asset:Asset>
        </rdfs:member>
     </rdf:Description>
     <rdf:Description rdf:about="#relationship1">
        <oslc_asset:relationshipType>
           <oslc_asset:RelationshipType rdf:about="http://example.com/oslc/relationships/Implementationy">
              <dcterms:title>Implementation</dcterms:title>
           </oslc_asset:RelationshipType>
        </oslc_asset:relationshipType>
     </rdf:Description>
     <rdf:Description rdf:about="#relationship2">
        <oslc_asset:relationshipType>
           <oslc_asset:RelationshipType rdf:about="http://example.com/oslc/relationships/Specification">
              <dcterms:title>Specification</dcterms:title>
           </oslc_asset:RelationshipType>
        </oslc_asset:relationshipType>
     </rdf:Description>
</rdf:RDF>

Delegated UI Examples

Selection dialog example

See Delegated UIs

Consumer IFrame embedding selection Dialog

<html>
...
window.addEventListener('message', receiver, false);
function receiver(e) {
  //Do something with the received results
}
....
<iframe src="http://example.com/assets/dialogs/pickasset"/>
...
</html>

Provider Dialog UI

<html>
....
//Handle post back search results
function respondWithPostMessage(/*string*/ response) {
    (window.parent | window).postMessage("oslc-response:" + response, "*");
}
...
</html>

Result format in JSON

{
    "oslc:results" : [{
            "oslc:label": "Myco Services Release",
            "rdf:resource": "http://example.com/oslc/assets/813/1.0" 
        }, {
            "oslc:label": "Myco Accounting App Release",
            "rdf:resource": "http://example.com/oslc/assets/23/3.5" 
        }
    ]
}

Preview UI

The build system fetched the preview UI from the asset management system to show on hover.

See UI Preview

Request

GET http://example.com/oslc/assets/813/1.0
Accept: application/x-oslc-compact+xml
OSLC-Core-Version: 2.0

Response

HTTP/1.0 201 Created
OSLC-Core-Version: 2.0
Content-Type: application/xml
ETag: xxx
Content-Length: nnn

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:oslc="http://open-services.net/ns/core#">
 <oslc:Compact
   rdf:about="http://example.com/oslc/assets/813/1.0">
   <dcterms:title> Myco Services Release </dcterms:title>
   <oslc:icon rdf:resource="http://example.com/icons/release.jpg" />
   <oslc:smallPreview>
      <oslc:Preview>
         <oslc:document rdf:resource="http://example.com/oslc/assets/813/1.0?hover=small" />
      </oslc:Preview>
   </oslc:smallPreview>
   <oslc:largePreview>
      <oslc:Preview>
         <oslc:document rdf:resource="http://example.com/oslc/assets/813/1.0?hover=large" />
         <oslc:hintWidth> 60em </oslc:hintWidth>
         <oslc:hintHeight> 20em </oslc:hintHeight>
      </oslc:Preview>
   </oslc:largePreview>
 </oslc:Compact>
</rdf:RDF>
]]> Mon, 27 Aug 2012 13:42 EDT <![CDATA[OSLC Asset Management 2.0 Appendix B: Resource Shapes]]> OSLC Administrator http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Appendix-B:-Resource-Shapes/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Appendix-B:-Resource-Shapes/#When:1345842331 An appendix of the [[OSLC Asset Management 2.0 Specification]]

[TOC]

Overview

This defines the definitions of the OSLC Asset Management 2.0 defined resources utilizing the OSLC Core Shape Resource definition. Implementations may use these shapes to as a basis for their work, providing their own property additions and additional constraints on OSLC defined properties.

Asset

<rdf:RDF 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"    
   xmlns:dcterms="http://purl.org/dc/terms/"    
   xmlns:foaf="http://xmlns.com/foaf/0.1/"    
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_cm="http://open-services.net/ns/asset#">

<oslc:ResourceShape
   rdf:about="http://example.com/oslc/shapes/Asset">

   <dcterms:title>Asset Management V2 Asset</dcterms:title>
   <oslc:describes rdf:resource="http://open-services.net/ns/asset#Asset" />
   <rdf:type rdf:resource="http://open-services.net/ns/core#ResourceShape" />   

   <!-- OSLC Core Common Properties -->
   <oslc:property>
      <oslc:Property>
         <oslc:name>identifier</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://purl.org/dc/terms/identifier" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>title</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/title" />
         <oslc:valueType rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>description</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/description" />
         <oslc:valueType rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>abstract</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/abstract" />
         <oslc:valueType
            rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>creator</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/creator" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:range rdf:resource="http://xmlns.com/foaf/0.1/Person" />
         <oslc:valueShape rdf:resource="http://example.com/oslc/shapes/Person" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-many" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>contributor</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/contributor" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:range rdf:resource="http://xmlns.com/foaf/0.1/Person" />
         <oslc:valueShape rdf:resource="http://example.com/oslc/shapes/Person" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-many" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>created</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/created" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
         <oslc:readOnly>true</oslc:readOnly>
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>modified</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/modified" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
         <oslc:readOnly>true</oslc:readOnly>
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>type</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#type" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#Resource" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#One-or-many" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Reference" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>serviceProvider</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/core#serviceProvider" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#Resource" />
         <oslc:range rdf:resource="http://open-services.net/ns/core#ServiceProvider" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Reference" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>instanceShape</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/core#instanceShape" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#Resource" />
         <oslc:range rdf:resource="http://open-services.net/ns/core#ResourceShape" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-many" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Reference" />
      </oslc:Property>
   </oslc:property>

   <!-- OSLC Asset additional properties -->   
   <oslc:property>
      <oslc:Property>
         <oslc:name>guid</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#guid" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>version</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#version" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>type</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/type" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>state</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#state" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>categorization</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#categorization" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>manufacturer</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#manufacturer" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>model</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#model" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>serialNumber</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#serialNumber" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>tag</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#tag" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-many" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>artifact</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#artifact" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Inline" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>artifactFactory</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#artifactFactory" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Reference" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Exactly-one" />
      </oslc:Property>
   </oslc:property>

   <!-- OSLC Artifact additional properties -->
   <oslc:property>
      <oslc:Property>
         <oslc:name>label</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/core#label" />
         <oslc:valueType rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>content</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#content" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#Resource" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Reference" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>format</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/format" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#string" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

   <oslc:property>
      <oslc:Property>
         <oslc:name>size</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#size" />
         <oslc:valueType rdf:resource="http://www.w3.org/2001/XMLSchema#integer" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
         <oslc:readOnly>true</oslc:readOnly>
      </oslc:Property>
   </oslc:property>

   <!-- Relationship properties -->
   <oslc:property>
      <oslc:Property>
         <oslc:name>relation</oslc:name>
         <oslc:propertyDefinition rdf:resource="http://purl.org/dc/terms/relation" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#Resource" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-many" />
      </oslc:Property>
   </oslc:property>

   <!-- Related resource reified statement properties -->
   <oslc:property>
      <oslc:Property>
         <oslc:name>relationshipType</oslc:name>
         <oslc:propertyDefinition
            rdf:resource="http://open-services.net/ns/asset#relationshipType" />
         <oslc:valueType rdf:resource="http://open-services.net/ns/core#AnyResource" />
         <oslc:representation rdf:resource="http://open-services.net/ns/core#Either" />
         <oslc:occurs rdf:resource="http://open-services.net/ns/core#Zero-or-one" />
      </oslc:Property>
   </oslc:property>

</oslc:ResourceShape>

</rdf:RDF>

foaf:Person

See OSLCCoreSpecRDFXMLExamples

]]> Fri, 24 Aug 2012 17:05 EDT <![CDATA[Implementation Reports]]> OSLC Administrator http://open-services.net/wiki/asset-management/Implementation-Reports/ http://open-services.net/wiki/asset-management/Implementation-Reports/#When:1345842167 Implementers of the OSLC Asset Management specifications are encouraged to place feedback on their experience (good and bad). To add a report, simply copy and paste a section template and fill out any necessary information.

[TOC]

OSLC Asset Management 2.0

This section gathers implementation reports for [[OSLC Asset Management 2.0 Specification]]

Providers

Rational Asset Manager

Contact information:

  • Reported by SrimanthGunturi
  • This capability was implemented in Rational Asset Manager 7.5.1.1.
  • Date of report: Feb 7, 2012
  • Date of availability: Mar 30, 2012

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: Provider
    • OSLC Asset Management 2.0 Providers tested with:
      • Rational Asset Manager 7.5.1.1

Table of supported capabilities: see OSLC-AssetManagement_2.0_Implementation_Report.xls attachment

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>

<2.0 template>

<Implementer> (copy and update template)

Contact information:

  • Reported by…
  • This capability was implemented in…
  • Date of report:
  • Date of availability: (indicate if estimated)

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: <consumer> and/or <service provider>
  • (if consumer, please add….)
    • OSLC Asset Management 2.0 Providers tested with:
      • (list out providers)

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>
]]> Fri, 24 Aug 2012 17:02 EDT <![CDATA[Meeting agendas and minutes]]> OSLC Administrator http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/ http://open-services.net/wiki/asset-management/Meeting-agendas-and-minutes/#When:1345839608 Meeting Agendas and Minutes for Asset Management

Meetings are held bi-weekly on Tuesday.

Time: 1:00 PM EDT

(contact Gili Mendel if you’d like to participate)

2.0 Meetings

14 August 2012

19 June 2012

8 May 2012

10 April 2012

13 March 2012

28 February 2012

14 February 2012

7 February 2012

31 January 2012

17 January 2012

03 January 2012

25 October 2011

11 October 2011

27 September 2011

31 August 2011

17 August 2011

3 August 2011

28 July 2011

6 July 2011

23 June 2011

25 May 2011

11 May 2011

28 July 2010

30 June 2010

26 May 2010

1.0 Meetings

17 Feb 2010

9 Sep 2009

26 Aug 2009

12 Aug 2009

29 July 2009

15 July 2009

1 July 2009

17 June 2009

]]> Fri, 24 Aug 2012 16:20 EDT <![CDATA[OSLC Asset Management Vocabulary]]> OSLC Administrator http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/ http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/#When:1345838949 Source file: [[File:asset.html | asset.html]]

The namespace URI for this vocabulary is:

http://open-services.net/ns/asset#

This page lists the RDFS classes and RDF properties that make up the OSLC Asset Management(Asset) vocabulary. Following W3C best practices, this information is available in HTML format (this page) and in RDFS format.

More details on how this page is generated and other related material can be found in the OSLC URI Naming Guidelines.

Description:

All vocabulary URIs defined in the OSLC Asset Management (Asset) namespace.

See Also:

RDFS Classes in this namespace

Artifact, Asset

RDF Properties in this namespace

artifact, artifactFactory, categorization, content, guid, identifier, manufacturer, model, relationshipType, serialNumber, size, state, tag, version

Artifact

http://open-services.net/ns/asset#Artifact Artifact is an RDFS class.

The Artifact fragment

See Also:

artifact

http://open-services.net/ns/asset#artifact artifact is an RDF property.

The multi valued list of artifacts.

See Also:

artifactFactory

http://open-services.net/ns/asset#artifactFactory artifactFactory is an RDF property.

Resource URI used to post new artifacts to the asset.

See Also:

Asset

http://open-services.net/ns/asset#Asset Asset is an RDFS class.

The Asset resource

See Also:

categorization

http://open-services.net/ns/asset#categorization categorization is an RDF property.

A categorization to classify an asset. The category schema values are defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.

See Also:

content

http://open-services.net/ns/asset#content content is an RDF property.

The media resource reference URI (the artifact bytes).

See Also:

guid

http://open-services.net/ns/asset#guid guid is an RDF property.

An identifier for the asset. Assigned by the service provider when a resource is created. Different versions of the same asset will share the same identifier.

See Also:

identifier

http://open-services.net/ns/asset#identifier identifier is an RDF property.

A unique identifier for a resource. Assigned by the service provider when a resource is created.

See Also:

manufacturer

http://open-services.net/ns/asset#manufacturer manufacturer is an RDF property.

The name of the asset manufacturer.

See Also:

model

http://open-services.net/ns/asset#model model is an RDF property.

The value of the asset model.

See Also:

relationshipType

http://open-services.net/ns/asset#relationshipType relationshipType is an RDF property.

The type of this relationship from the perspective of the oslc_asset:relatedAsset resource based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.

See Also:

serialNumber

http://open-services.net/ns/asset#serialNumber serialNumber is an RDF property.

The serial number assigned by the asset manufacturer.

See Also:

size

http://open-services.net/ns/asset#size size is an RDF property.

The size of the artifact media resource in bytes.

See Also:

state

http://open-services.net/ns/asset#state state is an RDF property.

Used to indicate the state of the asset based on values defined by the service provider. This specification does not define the resource for this property, however it should contain a dcterms:title property.

See Also:

tag

http://open-services.net/ns/asset#tag tag is an RDF property.

Specifies the asset tag value for an Asset. Asset tags are typically human readable labels. For hardware assets, these tags are durable, securely attached to equipment, and may also be readable by barcode and/or RFID.

See Also:

version

http://open-services.net/ns/asset#version version is an RDF property.

The version of the asset. Possible values may include ‘1.0’, ‘2.0’, etc.

See Also:

]]> Fri, 24 Aug 2012 16:09 EDT <![CDATA[Implementation Reports]]> OSLC Administrator http://open-services.net/wiki/asset-management/Implementation-Reports/ http://open-services.net/wiki/asset-management/Implementation-Reports/#When:1345838333 Implementers of the OSLC Asset Management specifications are encouraged to place feedback on their experience (good and bad). To add a report, simply copy and paste a section template and fill out any necessary information.

[TOC]

OSLC Asset Management 2.0

This section gathers implementation reports for [[OSLC Asset Management 2.0]]

Providers

Rational Asset Manager

Contact information:

  • Reported by SrimanthGunturi
  • This capability was implemented in Rational Asset Manager 7.5.1.1.
  • Date of report: Feb 7, 2012
  • Date of availability: Mar 30, 2012

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: Provider
    • OSLC Asset Management 2.0 Providers tested with:
      • Rational Asset Manager 7.5.1.1

Table of supported capabilities: see OSLC-AssetManagement_2.0_Implementation_Report.xls attachment

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>

<2.0 template>

<Implementer> (copy and update template)

Contact information:

  • Reported by…
  • This capability was implemented in…
  • Date of report:
  • Date of availability: (indicate if estimated)

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: <consumer> and/or <service provider>
  • (if consumer, please add….)
    • OSLC Asset Management 2.0 Providers tested with:
      • (list out providers)

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>
]]> Fri, 24 Aug 2012 15:58 EDT <![CDATA[Implementation Reports]]> OSLC Administrator http://open-services.net/wiki/asset-management/Implementation-Reports/ http://open-services.net/wiki/asset-management/Implementation-Reports/#When:1345838288 Implementers of the OSLC Asset Management specifications are encouraged to place feedback on their experience (good and bad). To add a report, simply copy and paste a section template and fill out any necessary information.

[TOC]

OSLC Asset Management 2.0

This section gathers implementation reports for [[OSLC Asset Management 2.0]]

Providers

Rational Asset Manager

Contact information:

  • Reported by SrimanthGunturi
  • This capability was implemented in Rational Asset Manager 7.5.1.1.
  • Date of report: Feb 7, 2012
  • Date of availability: Mar 30, 2012

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: Provider
    • OSLC Asset Management 2.0 Providers tested with:
      • Rational Asset Manager 7.5.1.1

Table of supported capabilities: see OSLC-AssetManagement_2.0_Implementation_Report.xls attachment

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>

<2.0 template>

<Implementer> (copy and update template)

Contact information:

  • Reported by…
  • This capability was implemented in…
  • Date of report:
  • Date of availability: (indicate if estimated)

Details about support:

  • Specification version supported: OSLC Asset Management 2.0
  • Implementation supported: <consumer> and/or <service provider>
  • (if consumer, please add….)
    • OSLC Asset Management 2.0 Providers tested with:
      • (list out providers)

Additional details about support: (not noted in table)

  • Subset of specs supported and why:
    • …
  • Deviations from specs and why:
    • …

Issues:

  1. <issues>

Worked well:

  • <good things>
]]> Fri, 24 Aug 2012 15:58 EDT <![CDATA[index]]> OSLC Administrator http://open-services.net/wiki/asset-management/ http://open-services.net/wiki/asset-management/#When:1345149327 Welcome to the opening page of your EE Wiki!

]]> Thu, 16 Aug 2012 16:35 EDT