- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Thu, 1 May 2014 22:55:53 +0200
- To: <public-hydra@w3.org>
On Sunday, April 27, 2014 6:31 PM, Gregg Kellogg wrote:
> On Apr 27, 2014, at 8:15 AM, Markus Lanthaler wrote:> >
> >> On Sunday, April 27, 2014 4:58 PM, Gregg Kellogg wrote:
> >>> On Apr 27, 2014, at 7:34 AM, "Markus Lanthaler" wrote:
> >>> I see. That certainly works (already). You can do it without OWL by
> >>> simply materializing that triple, which is very cheap to do for the
server
> >>> and eliminates the reasoning for the client. The issue however is that
it
> >>> could quite easily be misinterpreted as a link instead of a templated
link
> >>> (by humans):
> >>>
> >>> {
> >>> "@type": "InterestCollection",
> >>> "searchInterestCollection": "/apidoc#SearchInterestValue"
> >>> }
> >>
> >> It may be that saying TemplatesLink is a subclass of Link is wrong, or
> >> that they are disjoint. It's the result of applying variable
substitution to
> >> the template which is a Link.
> >
> > Right. That's the reason why TemplatedLink is currently *not* a subclass
of
> > Link. They are both subclasses of rdf:Property.
>
> Sorr, on my iPad, and don't have the documentation in front of me. Do we
need to assert
> that they are disjoint? If they are, then I don't see how a client would
confuse the value of a
> TemplatedLink property with a Link.
No, I'm not worried about machines, I'm worried about humans making
mistakes. Declaring them as disjoint unfortunately wouldn't help much in
that regard.
> >> Yes, but I think this is pretty clear, but requires more work on the
> >> semantics of TemplatesLink, IMO.
> >
> > What's semantics is TempledLink missing?
>
> That the result of manifesting a template to an IRI after variable
substitution is a Link; I'm
> not sure how you might express this, though. Probably just claiming this
in the spec is
> sufficient.
Hmm... doesn't the term TemplatedLink clearly imply that? Do you have some
concrete wording that we could put in the spec to clarify this even further?
--
Markus Lanthaler
@markuslanthaler
Received on Thursday, 1 May 2014 20:56:20 UTC