RE: concerns about hydra:mappings (ISSUE-30)

On Tuesday, February 18, 2014 8:11 PM, Ruben Verborgh wrote:
> > Right. If that information would be in the representation at /hilton it
> > would be included in the result following that model. In my example,
that
> > information wasn't there though.
> 
> So if the model is extended later, it would suddenly match?

Yes. It's really the same as with an HTML document. As soon as you add more
information to it, it will start to match more queries.


> I think it would be reasonable to assume, in the case of blockbuster,
> that it would only show actors who have been involved in blockbuster
> movies (and not happen to have dated somebody who did.)
> That's an expectation we have. can we convey that expectation to
> machines?

We should surely try


> > I think the explanation above clarifies it. If /hilton would contain the
> > information above, it would be included in the result set.
> 
> But this couples your search results to your document's representation
> structure?

No, quite the contrary. It ignores the structure completely and just looks
for matching property-value pairs--regardless of where they are in the
representation.


> GET /hilton
> 
> :Paris_Hilton :gender :Female.
> :Paris_Hilton :hasParent :Richard_Hilton.
> :Paris_Hilton :hasParent :Kathy_Hilton.
> :Richard_Hilton :gender :Male.
> :Kathy_Hilton :gender :Female.
> 
> would mean that
> 
> /actors?gender=Male
> 
> could contain :Paris_Hilton?

Yes, just as a simple keyword search for "male" would return /hilton.


> >> That would be quite arbitrary
> >
> > Just as arbitrary as a Google search is in principle :-P
> 
> Yes, but then there's a human behind the controls to interpret.
> Machines can't do that amount of interpretation.

Why not? If you need something more specific, you can always filter the
results locally (just as a human does).


Cheers,
Markus


--
Markus Lanthaler
@markuslanthaler

Received on Friday, 28 February 2014 15:25:15 UTC