[oslc-core] Suggested improvements to new "Link Guidance"

[Steve K Speicher]

Additional suggest for this guidance:
In 5. it states 
"When defining a new vocabulary with link types, there should be exactly 
one predicate for each link type concept. That is, there should not be 
defined two different link predicates representing the same thing, with 
just the subject and object reversed (e.g. validates / validatedBy )."

This doesn't cover the case where both end of the link now store the link, 
we just have 1 predicate to represent the redundant statement.  We should 
include a subbullet to that guidance that reads: "There should be only a 
single authority for the link relationship to prevent data skew.  (see 
above)  If needed, additional tools/servers/DBs may cache this statement."

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> 
http://open-services.net

"Oslc-Core" <oslc-core-bounces at open-services.net> wrote on 06/01/2013 
11:41:01 AM:

> From: Steve K Speicher/Raleigh/IBM at IBMUS
> To: oslc-core at open-services.net
> Date: 06/01/2013 11:41 AM
> Subject: [oslc-core] Suggested improvements to new "Link Guidance"
> Sent by: "Oslc-Core" <oslc-core-bounces at open-services.net>
> 
> These comments are in reference to emerging Link guidance [1]
> 
> The first "OSLC Core 3.0 Linked Guidance"
> says  "Whenever possible links should be stored in the graph identified 
by 
> the subject URI. "
> 
> I suggest replacing with something like this:
> "The link (statement) should be stored with the tool (document) that 
> asserts the relationship."
> 
> Including, perhaps a footnote or sub-bullets, that there are number of 
> factors that are involved when a tool determines where to assert the 
link:
> 1. if other tool is offline, therefore cannot assert the link
> 2. if modifying one resource, a new revision will be generated, but 
other 
> resource isn't modified.
> 3. might need a license on the other tool I don't have
> 4. UX in tool where user is creating link is poor, as it may take a 
while 
> to render the link that just got added, due to index latency
> 5. access control may prevent end user from creating in one of the tools
> 
> 
> [1] http://open-services.net/wiki/core/Links/
> 
> Thanks,
> Steve Speicher
> IBM Rational Software
> OSLC - Lifecycle integration inspired by the web -> 
> http://open-services.net
> 
> 
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
>