Re: [core] ue of resource type in collections

[Peter van der Stok <[e-mail]>]

Thanks Klaus for the comments.
The new resource types have to be registered, and can then be used in an
interoperable way for discovery.
That makes it difficult to not prescribe them in the draft.
Given that some of the resources in the collection are not compulsory to
have,
I will provide the more extensive example no 2 in est-coaps.

Greetings,

Peter
Klaus Hartke schreef op 2018-07-18 11:00:

> Peter van der Stok wrote: 
> 
>> The coaps-est server uses a collection of resources:
>> The collection resource has been assigned rt=ace.est
>> It is not clear what the resource types of the underlying resources should
>> be.
> 
> According to BCP 190 [1 [1]], the coaps-est draft should not mandate particular forms of URI substructure. So a server should be free to structure URIs as it sees fit, e.g.:
> 
> </a>;rt="ace.est"
> </b>;rt="ace.est"
> </c>;rt="ace.est"
> </d>;rt="ace.est"
> </e>;rt="ace.est"
> </f>;rt="ace.est"
> 
> If a client has trouble selecting the right link from the above list (and they all look interchangeable to me), then you'd need to provide more specific link information, e.g.:
> 
> </a>;rt="ace.est.skg"
> </b>;rt="ace.est.crts"
> </c>; rt="ace.est"
> </d>;rt="ace.est.att"
> </e>;rt="ace.est.sren"
> </f>;rt="ace.est.sen"
> 
> Klaus
> 
> [1] https://tools.ietf.org/html/bcp190
 

Links:
------
[1] https://tools.ietf.org/html/bcp190