Noob question - Asset URI?

There is no "formal way" to construct an Asset URI... but you can see the pattern if you play with RAM's REST api: https://jazz.net/wiki/bin/view/Main/RamRestApiMain

<server>/<context>/olsc/assets/<GUID>/<VERSION>

e.g.

http://ramlnx:9080/ram/oslc/assets/{EE98FB34-280B-9EBB-B46B-7748E90EF076}/1.0

If you do not have on your accept header application/xml, RAM will reroute you to the corresponding web page (for asset detail).

There is no "formal way" to construct an Asset URI... but you can see the pattern if you play with RAM's REST api: https://jazz.net/wiki/bin/view/Main/RamRestApiMain

<server>/<context>/olsc/assets/<GUID>/<VERSION>

e.g.

http://ramlnx:9080/ram/oslc/assets/{EE98FB34-280B-9EBB-B46B-7748E90EF076}/1.0

If you do not have on your accept header application/xml, RAM will reroute you to the corresponding web page (for asset detail).

Hi,

Thanks. However it sends html even if I have application/xml. Here's my header accept (I have Tabulator - disappointed not to see some RDF from RAM )-:

text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,application/rdf+xml;q=0.93,text/rdf+n3;q=0.5

Your accept headers are evaluated in the order in which you send them. Because you're sending 'text/html' first the server is returning html. The server is looking for the accept header 'application/xml'. If you include this first (accept=application/xml) the response from the server will be RDF.

You can see our progress on RDF in RAM here. http://open-services.net/bin/view/Main/AssetHome . RAM supports the 1.0 OSLC Asset Management Specification and we're in the process of defining the 2.0 specification. If you have any input on the specification we would be more than happy to listen.

Your accept headers are evaluated in the order in which you send them. Because you're sending 'text/html' first the server is returning html. The server is looking for the accept header 'application/xml'. If you include this first (accept=application/xml) the response from the server will be RDF.

You can see our progress on RDF in RAM here. http://open-services.net/bin/view/Main/AssetHome . RAM supports the 1.0 OSLC Asset Management Specification and we're in the process of defining the 2.0 specification. If you have any input on the specification we would be more than happy to listen.

Thanks. One thing I'd like to see in RAM is a link on the web user interface which when clicked, goes directly to the OSLC URL for the asset. Likewise there should be a link for RDF triplification of the asset and it's related assets down to a particular depth.

I also think there should be more use of the OSLC URIs in the Java identification API. After all, the OSLC URI is the globally unique id for the asset.

Cheers

Your accept headers are evaluated in the order in which you send them. Because you're sending 'text/html' first the server is returning html. The server is looking for the accept header 'application/xml'. If you include this first (accept=application/xml) the response from the server will be RDF.

You can see our progress on RDF in RAM here. http://open-services.net/bin/view/Main/AssetHome . RAM supports the 1.0 OSLC Asset Management Specification and we're in the process of defining the 2.0 specification. If you have any input on the specification we would be more than happy to listen.

Hi,

RAM is sending the wrong mime type for oslc URLs. It should be application/rdf+xml

see this:

on hitting URL: https://<server>/ram/oslc/assets/3C046816-74B0-9EFB-385F-0317FCC0EFDB/1.0.6.82

Firebug reports:

Date Thu, 16 Jun 2011 00:30:46 GMT
Content-Type text/xml;charset=UTF-8
Content-Language en-AU
Last-Modified Thu, 01 Jan 1970 00:00:00 GMT
Etag NDQzx
Vary Accept-Encoding
Server Microsoft-IIS/6.0, WebSphere Application Server/7.0
Content-Encoding gzip
Transfer-Encoding chunked
Request Headersview source
Host assetmgr.apps.anz
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17
Accept application/rdf+xml,application/xml,*/*;q=0.8,text/html,application/xhtml+xml
Accept-Language en-gb,en;q=0.5
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7

Looks like a candidate for a PMR to me.

The references in RDF files served by RAM are not found. Included in the list are

http://jazz.net/xmlns/ecalm/ram/internal/v7.2community
http://jazz.net/xmlns/ecalm/ram/internal/v7.2reference
http://open-services.net/xmlns/asset/1.0/artifact
http://open-services.net/xmlns/asset/1.0/artifactContentFactory
http://open-services.net/xmlns/asset/1.0/asset
http://open-services.net/xmlns/asset/1.0/etag
http://open-services.net/xmlns/asset/1.0/size
http://open-services.net/xmlns/asset/1.0/state

This is quite annoying because RDF viewers cannot access the Ontology.

Where are the RDF files?

RAM is sending the wrong mime type for oslc URLs. It should be application/rdf+xml

see this:

on hitting URL: https://<server>/ram/oslc/assets/3C046816-74B0-9EFB-385F-0317FCC0EFDB/1.0.6.82

Firebug reports:

Date Thu, 16 Jun 2011 00:30:46 GMT
Content-Type text/xml;charset=UTF-8
Content-Language en-AU
Last-Modified Thu, 01 Jan 1970 00:00:00 GMT
Etag NDQzx
Vary Accept-Encoding
Server Microsoft-IIS/6.0, WebSphere Application Server/7.0
Content-Encoding gzip
Transfer-Encoding chunked
Request Headersview source
Host assetmgr.apps.anz
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17
Accept application/rdf+xml,application/xml,*/*;q=0.8,text/html,application/xhtml+xml
Accept-Language en-gb,en;q=0.5
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7

Looks like a candidate for a PMR to me.

RAM currently implements the 1.0 Asset Management OSLC specification which includes some RDF tags, but is not valid RDF. This is why it's returning the application/xml mime type. The OSLC 2.0 Asset Management specification will be valid RDF and will return the application/rdf+xml mime type.

The references in RDF files served by RAM are not found. Included in the list are

http://jazz.net/xmlns/ecalm/ram/internal/v7.2community
http://jazz.net/xmlns/ecalm/ram/internal/v7.2reference
http://open-services.net/xmlns/asset/1.0/artifact
http://open-services.net/xmlns/asset/1.0/artifactContentFactory
http://open-services.net/xmlns/asset/1.0/asset
http://open-services.net/xmlns/asset/1.0/etag
http://open-services.net/xmlns/asset/1.0/size
http://open-services.net/xmlns/asset/1.0/state

This is quite annoying because RDF viewers cannot access the Ontology.

Where are the RDF files?

As far as I can tell an Ontology was not distributed with the 1.0 Asset Management specification. One will be made available for the 2.0 specification so that the namespace URLs will resolve.

The references in RDF files served by RAM are not found. Included in the list are

http://jazz.net/xmlns/ecalm/ram/internal/v7.2community
http://jazz.net/xmlns/ecalm/ram/internal/v7.2reference
http://open-services.net/xmlns/asset/1.0/artifact
http://open-services.net/xmlns/asset/1.0/artifactContentFactory
http://open-services.net/xmlns/asset/1.0/asset
http://open-services.net/xmlns/asset/1.0/etag
http://open-services.net/xmlns/asset/1.0/size
http://open-services.net/xmlns/asset/1.0/state

This is quite annoying because RDF viewers cannot access the Ontology.

Where are the RDF files?

As far as I can tell an Ontology was not distributed with the 1.0 Asset Management specification. One will be made available for the 2.0 specification so that the namespace URLs will resolve.

So the Ontology doesn't exist at all for 1.0.
Smooth.

Your accept headers are evaluated in the order in which you send them. Because you're sending 'text/html' first the server is returning html. The server is looking for the accept header 'application/xml'. If you include this first (accept=application/xml) the response from the server will be RDF.

Actually, the accept header is evaluated based on quality first, then order. So for the accept header:

text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,application/rdf+xml;q=0.93,text/rdf+n3;q=0.5

text/html and application/xhtml+xml take precedence over the rest (by default, q=1.0). And of those, text/html is first so that's what is returned. Any mime types that can't be handled by the server are of course ignored. If those two were removed:

application/xml;q=0.9,*/*;q=0.8,application/rdf+xml;q=0.93,text/rdf+n3;q=0.5

application/rdf+xml would take precedence, then application/xml and so on.