Update how link header works in CollectionService

[ruebot]

Should provide a link header that links to the membership in the indirect container with a rel of members.

[DiegoPino]

Hi, i have been trying to get a good notion of existing "rel" values, and i shoud ask @Islandora-CLAW/7-x-2-x-sprinters about this:
http://microformats.org/wiki/existing-rel-values
It's ok to invent a new rel? or should we try to make our links fit into something already existing?

"member" is there but with a different meaning,
On the other hand, json-ld has "collection" also which is closer maybe?

Suggestions?

[DiegoPino]

Since the link involves an islandora service resource endpoint, we could in the future return instead the members service endpoint( putting new members for example) using something like this
http://tools.ietf.org/html/rfc6861

[ruebot]

Well, it surely isn't rel=sweetheart

[DiegoPino]

@ruebot, so we go for rel=crush instead 😄

[whikloj]

Just based on how Apple and DCTerms are specified in that list, should we consider something like rel="islandora-member" or rel="pcdm-member"?

[acoburn]

I would be very careful about adding new rel values. Instead, I'd recommend using values from this list: http://www.iana.org/assignments/link-relations/link-relations.xhtml

[DiegoPino]

@acoburn, you are right, that is the reason i added the list in the first place. In the iana world, there is relation named create-form, i'm very tempted to view LDP indirect and direct containers as an RDF abstraction of this…because i don't know what we could assign to this particular /member resource, that in reality is just an automa"gic" triple generator

[daniel-dgi]

@DiegoPino I like your comment about providing the other relevant API endpoints instead of LDP specifics, which are really just behind the scenes implementation details. We just need to figure out those endpoints! But I definitely could see us providing links to a endpoint that would list all members for a collections. And definitely the add/remove member endpoints too.

[DiegoPino]

@daniel-dgi++, we will know more about this when we finish those endpoints. Good to know we are in sync with this.
Also @acoburn, maybe iania's rel=hub ?

Refers to a hub that enables registration for notification of updates to the context.

could be also a free interpretation of an indirect/direct container. LDP should have their own 😄

[ruebot]

So, this one is taken care of right? We just need to sort out this one, because "member" is not in this list?

[DiegoPino]

@ruebot, member is not in iana's list, but it's valid one. If we go for iana i would suggest for now "hub"

[ruebot]

I'm good with hub. @Islandora-CLAW/7-x-2-x-committers what do y'all think?

[ruebot]

@whikloj, @daniel-dgi are we good with hub? If so, then @DiegoPino can update #152 and we should be good for a merge there.

[daniel-dgi]

hub's fine for now. i'm sure we'll go back and forth on this a lot over time. but let's merge it in! i like it.

[DiegoPino]

Ok, updated #152, hub it is.

[ruebot]

Resolved with 238cfb4