Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lyo-dev] How to using the AM domain resource type Link Type

Hi Jean-Luc,

The link type resource that you mention is being deprecated.  Its original intent was to provide meta information about specific link type predicates that are supported by the specific implementation of the service provider.  It is being deprecated and functionality is being supplied by resource shapes, and standard LDP principals of resolving the predicate URI directly.  With that said resource shapes are not a MUST in any of the specifications, and only partially implemented in out products (and not at all in Design Management 4.x).

When it comes to specific integrations of Rational OSLC products, the story is a little more confusing.  Not all OSLC service providers are expected to support all possible link type predicates as properties of their resources.  Additionally there is a history of how links across OSLC domains are implemented.

In Design Management we tried to take the most flexible and customizable approach.  We wrote an article describing the current state of linking here: https://jazz.net/library/article/1111

It is not a pretty picture, but it was accurate at the time of writing.  Not much has changed in the 4.x versions of the Jazz OSLC service providers (RTC/RRC/RQM/DM), so this article is still accurate.  
I hope this helps.


jim conallen
Rational Design Management (DM) Lead Architect, OSLC AM Lead
jconallen@xxxxxxxxxx
Rational Software, IBM Software Group



Inactive hide details for "Johnson, Jean-Luc" ---03/25/2014 12:27:38 PM---  Hi OSLC community,"Johnson, Jean-Luc" ---03/25/2014 12:27:38 PM---  Hi OSLC community,

From: "Johnson, Jean-Luc" <Jean-Luc.Johnson@xxxxxxxx>
To: <lyo-dev@xxxxxxxxxxx>,
Date: 03/25/2014 12:27 PM
Subject: [lyo-dev] How to using the AM domain resource type Link Type
Sent by: lyo-dev-bounces@xxxxxxxxxxx





 
Hi OSLC community,
 
I’m using the OSLC AM domain with my application. See specification at http://open-services.net/wiki/architecture-management/OSLC-Architecture-Management-Specification-Version-2.0/ . Basically I grabbed the code http://git.eclipse.org/c/lyo/org.eclipse.lyo.client.git/tree/org.eclipse.lyo.client.java/src/main/java/org/eclipse/lyo/client/oslc/resources/ArchitectureResource.java  and http://git.eclipse.org/c/lyo/org.eclipse.lyo.client.git/tree/org.eclipse.lyo.client.java/src/main/java/org/eclipse/lyo/client/oslc/resources/ArchitectureLinkType.java 
 
The implementation of the architecture resource is quite obvious. But when it comes to the link type resource I have the feeling that I miss the concept. The spec says:
Link Type (LT) - A URI that represents the type of a link. In semantic web terminology it is the predicate of an RDF triple. It clarifies the type of relationship between two resources. Link Type URIs may be defined locally, within the OSLC, or externally (i.e. Dublin Core terms). Link types could be defined in RDF Schemas.”
 
I don’t see any properties that mention the two resources. Then how that is work? Do you have any example?
 
This lead me to my second question:
At this moment, RTC can consume my OSLC Service provider application. How can I save back the link to my application. Unfortunately the AM resource doesn’t have relationship properties like the Requirement resource for example. I have attached a snapshot picture of the message I received from RTC.
 
Thank you for your support.
 
SaveLinkBack.png
 
 
Best regards,
Jean-Luc Johnson_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev

GIF image

GIF image


Back to the top