[oslc-AssetMgmt] Questions about OSLC Asset Management

[Thunissen Marc]

Hello,
 
I am currently working on integrating an asset manager in a project.
I want to be able to replace the selected asset manager by another one, if necessary, so I think using the OSLC Asset Management specification could be a very good point.
 
So I am trying to understand the current specification.
I already played with OSLC a little bit, implementing a OSLC-RM and OSLC-CM interface of our HP Quality Center.
 
I have a few questions about the specification version 2.0 draft.
 
1. I see two different naming spaces for the asset management:
 - http://open-services.net/xmlns/oslc-asset-2.0# (in the Namespaces section)
 - http://open-services.net/ns/asset# (in the OSLC Asset Management Resource Definitions section)
Is there really two namespaces to use ?

2. In the asset properties I see an oslc:label.
Does "oslc" mean http://open-services.net/ns/core# ?
The value-type here is XMLLiteral while it is defined as a String in the http://open-services.net/ns/core# resources.
Is this correct ?
 
3. Can you confirm that I have well understood the way a client can create an asset with some artifacts:
 
>> for the asset
 client> POST an asset resource on the creation factory URL specified by the service provider
 server> return an HTTP 201 and a "location" header with the URL of the asset.
 client> GET the new asset URL to read the oslc_asset:artifactFactory property.
 server> return the asset resource with the additional properties
 
>> for each artifact
 client> POST the artifact content to the URL of the oslc_asset:artifactFactory, specifying the mime type
 server> save the artifact content somewhere and create an URL to make it available, add an artifact property value to the asset, setting the URL, format, size and modification date, then return an HTTP 201 and a "location" header with the URL of the artifact content.
 
I have the following problem with this:
 a. How can I set the dc:title and oslc:label of the artifact ?
    The URL returned is the one of the artifact content, not of the artifact resource (is that right ?).
    So should I get the full asset, enum the artifacts, find the one having the right URL then update the full asset ?
 b. This means that the artifact content belongs to the OSLC asset manager, we cannot make a reference to something already archived somewhere !?
 c. If we have to introduce a new version of an existing asset with 99% of the artifacts unchanged, we need to post (and store) them all once more !?
 
4. I saw that RAS was involved in the properties of the artifact before, but this has been removed in r29 of the specification.
This there a will to restablish a link with RAS later ?
 
Best regards,
 
Marc
 

_____________________________________________________________________________

Marc Thunissen ( OSL 31 )

Software Architect

Océ Software Laboratories Namur sa

Parc Créalys - Bâtiment Capella

rue Jean Sonet, 4 - 5032 GEMBLOUX

Tel: +32 81 876 744

Fax : +32 81 876 810

mailto:Marc.Thunissen at oce.com <mailto:Marc.Thunissen at oce.com> 

http://www.osl.be <http://www.osl.be/> 

http://www.oce.com <http://www.oce.com/> 

 


This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-assetmgmt_open-services.net/attachments/20110802/a97744d9/attachment-0003.html>