Accessing RCAM / DM programmatically
2 answers
Presently the only "official" API is the OSLC AM and RM interfaces. Even with these the only information being returned are the resource title, identifier, type, and the 'OSLC style' links that were established in DM.
I am preparing a wiki page on this topic, and hope to have it posted soon. There you will see what kind of information is available.
In the meantime, if you want to try things out, and have a tool like Poster installed in Firefox, try GETing a resource from DM with the following headers:
Accept: application/rdf+xml
OSLC-Core-Version: 2.0
The resource URI will be of the form: https://host:9443/rmps/models/123
where host is your server's hostname, and 123 is the simple identifier of the resource. This is only valid for RSA supplied resources. Rhapsody supplied resources use a slightly different URI pattern.
I am preparing a wiki page on this topic, and hope to have it posted soon. There you will see what kind of information is available.
In the meantime, if you want to try things out, and have a tool like Poster installed in Firefox, try GETing a resource from DM with the following headers:
Accept: application/rdf+xml
OSLC-Core-Version: 2.0
The resource URI will be of the form: https://host:9443/rmps/models/123
where host is your server's hostname, and 123 is the simple identifier of the resource. This is only valid for RSA supplied resources. Rhapsody supplied resources use a slightly different URI pattern.
Hi James,
Even if the access to known elements works ...
Type: Content-Type: application/ntriples;charset=UTF-8
<https://somehost:9443/rmps/models/200> <http://xmlns.com/foaf/0.1/primaryTopic> <https://somehost:9443/rmps/models/200> .
<https://somehost:9443/rmps/models/200> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.eclipse.org/uml2/3.0.0/UML#Class> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/emf/2002/Ecore#EModelElement.eAnnotations> _:MD0 .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq> .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_1> <https://somehost:9443/rmps/models/200#annotation_0> .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_2> <https://somehost:9443/rmps/models/200#annotation_1> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/uml2/3.0.0/UML#Element.ownedComment> _:MD1 .
_:MD1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq> .
_:MD1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_1> <https://somehost:9443/rmps/models/200#_gBMxwRJBEd-S6pMNLAdfTA> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/uml2/3.0.0/UML#NamedElement.name> "Classname"^^<http://www.eclipse.org/uml2/3.0.0/UML#String> .
...
the questions arise, when a query with a service will be possible. In the above case, I see a element with a number of 200, but it would be nicer to be able to search and browse by qualified name. Will there be a date, when this functionality should be incooperated?
TIA
Rainer
Even if the access to known elements works ...
Type: Content-Type: application/ntriples;charset=UTF-8
<https://somehost:9443/rmps/models/200> <http://xmlns.com/foaf/0.1/primaryTopic> <https://somehost:9443/rmps/models/200> .
<https://somehost:9443/rmps/models/200> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.eclipse.org/uml2/3.0.0/UML#Class> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/emf/2002/Ecore#EModelElement.eAnnotations> _:MD0 .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq> .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_1> <https://somehost:9443/rmps/models/200#annotation_0> .
_:MD0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_2> <https://somehost:9443/rmps/models/200#annotation_1> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/uml2/3.0.0/UML#Element.ownedComment> _:MD1 .
_:MD1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq> .
_:MD1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#_1> <https://somehost:9443/rmps/models/200#_gBMxwRJBEd-S6pMNLAdfTA> .
<https://somehost:9443/rmps/models/200> <http://www.eclipse.org/uml2/3.0.0/UML#NamedElement.name> "Classname"^^<http://www.eclipse.org/uml2/3.0.0/UML#String> .
...
the questions arise, when a query with a service will be possible. In the above case, I see a element with a number of 200, but it would be nicer to be able to search and browse by qualified name. Will there be a date, when this functionality should be incooperated?
TIA
Rainer