search

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
139 stars 25 forks source link

Describe/specify how the target IRI for an hydra:operation is resolved #100

Open vanthome opened 9 years ago

vanthome commented 9 years ago

Although it is intuitive/ logical, that the target IRI is (by default) the IRI defined by the @id of the closest subject of the hydra:operation, this should be specified or at least documented. I think this part is not yet covered by anything in surrounding specs like JSON-LD.

cr3a7ure commented 7 years ago

I'll put here another question as it seems relevant.

When we define a hydra:Class we know:

  1. is dereferenceable
  2. has suportedOperations
  3. has instances

How we should guide the client in order to know that /thing/{id} is the IRI for an instance of this class? We can not assign this as an @id and the whole Class node has no other IRI. Should we use hydra:Link or hydra:TemplatedLink as an rdf:Property of a Class? That way we are just looking for hydra:Link term in order to proceed, whether it is used as a class or a property.

RubenVerborgh commented 7 years ago

How we should guide the client in order to know that /thing/{id} is the IRI for an instance of this class?

That's not something the client should know. Rather, the client should know: what is the IRI of this particular instance?

Should we use hydra:Link or hydra:TemplatedLink as an rdf:Property of a Class?

hydra:TemplatedLink

tpluscode commented 6 years ago

How we should guide the client in order to know that /thing/{id} is the IRI for an instance of this class?

Issue #50 has a possible solution