Re: 22.9 oslc-op Weekly Contributors Meeting
|
You could just use a normative table of outgoing and incoming link types (i.e., property and inverse properties). However, it would be nice if this was machine readable, and an extension to ResourceShapes would do that.
We could also decide to declare property and inverse properties in the OSLC vocabularies. That wouldn’t require any extensions. Since OSLC does not rely on RDF inferencing, this shouldn’t create any problems.
From: <oslc-op@...> on behalf of Eran Gery <eran.gery@...>
Ed, Jim did not accept the text as he is not sure that the “store on outgoing side” is respected by ELM. Can you comment on that. One comment I have is that it is enough that it is the 90% case as a principle. We can document exceptions. ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd Ed,
Jim did not accept the text as he is not sure that the “store on outgoing side” is respected by ELM. Can you comment on that. One comment I have is that it is enough that it is the 90% case as a principle. We can document exceptions. There are clearly exceptions in opt-out mode that there are still backlinks with CCM. We can document that as an exception. Jim suggested that we may have to use OSLC shapes to determine the owner, IMO it is a no go for the reason that the maturity level of the bi-diretional profile is far from mandating OSLC shapes. Actually, none of the linking profile require support for shapes. So the only options I see
Please speak up…
Eran
From: oslc-op@... <oslc-op@...>
On Behalf Of "Eran Gery"
Sent: Thursday, 22 September 2022 15:59 To: Gentry, Edward <e.gentry@...> Cc: oslc-op@... Subject: [EXTERNAL] Re: [oslc-op] 22.9 oslc-op Weekly Contributors Meeting
Ed Please review the link ownership text Link ownership In bi-derctional linking scenarios both OSLC participants are aware of links across their owned resources and enable link visibility and navigation at each side. Nevertheless ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd Ed
Please review the link ownership text
Link ownership
In bi-derctional linking scenarios both OSLC participants are aware of links across their owned resources and enable link visibility and navigation at each side. Nevertheless, storing a link at both sides is considered an ill-practice as it is essentially replication of data. This may result in inconsistencies as links are updated or deleted, since maintaining consistency requires synchronization across the providers on any update. Therefore, the recommended practice is to store links on one of the participants, and use link discovery by the other participant. Therefore, there needs to be an agreed convention on which side should store the link. OSLC links have an incoming and outgoing sides, determined by the role of the link. Usually one side will have an active predicate name, for example "implements" and the other side will have a passive predicate name, in this example it would be "implemented by". The active side is also considered the outgoing side, and the passive the incoming side. The convention is that the link is stored with the resource on the outgoing side, i.e. the resource with the active predicate. The incoming side would discover the links with one of the discovery methods discussed in the following sections. Note the creation of the link may be initiated by both providers. In case that the link is initiated by the incoming side provider, it needs to store it with the resource on the outgoing side provider. This is discussed in the put on resources section.
Thanks eran
From: Gentry, Edward <e.gentry@...>
Hi All, I’m traveling today and so will miss our meeting this afternoon. @David Honey2, could you please arrange a meeting with John Vasta for me regarding the authentication in the link Profile? We should be able to keep it to 30 minutes. ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd Hi All,
I’m traveling today and so will miss our meeting this afternoon.
@David Honey2, could you please arrange a meeting with John Vasta for me regarding the authentication in the link Profile? We should be able to keep it to 30 minutes. Find something that works for him in the morning and I’ll make it work.
Cheers,
Ed |
||||||||||||
|
|