Re: [core] ue of resource type in collections

Hi Klaus

I understand that resource assignments are not compulsory, only recommended. Avoiding conflicts between these recommendations within IETF and with other well known ecosystems should just benefit the CoAP community.

Michel

-----Original Message-----
From: Klaus Hartke [mailto:klaus.hartke@ericsson.com] 
Sent: Thursday, July 19, 2018 10:14 AM
To: Michel Veillette <Michel.Veillette@trilliant.com>; consultancy@vanderstok.org; Core <core@ietf.org>
Subject: RE: [core] ue of resource type in collections

Hi Michel,

the point is that a server is free to organize its URI space as it sees fit and link annotations are needed to find the right resource.

It's not possible to reserve URI paths for any purpose (with the exception of .well-known paths). You can use /c in your examples if you want, but you cannot mandate that implementations do the same or claim it for CoMI. And I don't think it's time well spent if we'd try to ensure that no example uses a path that already appears in another example.

Klaus

> -----Original Message-----
> From: Michel Veillette <Michel.Veillette@trilliant.com>
> Sent: Thursday, 19 July, 2018 15:55
> To: Klaus Hartke <klaus.hartke@ericsson.com>; 
> consultancy@vanderstok.org; Core <core@ietf.org>
> Subject: RE: [core] ue of resource type in collections
> 
> The recommended list of CoAP resources listed in the original email 
> conflict with current CoMI recommended resource (/c). To minimize the 
> likelihood of conflicts, I recommend to define these resources under a 
> single root resource.
> 
> For example:
> </est/skg>;rt="ace.est.skg"
> </est/crts>;rt="ace.est.crts"
> </est>; rt="ace.est"
> </est/att>;rt="ace.est.att"
> </est/sren>;rt="ace.est.sren"
> </est/sen>;rt="ace.est.sen"
> 
> Regards,
> Michel
> 
> -----Original Message-----
> From: core [mailto:core-bounces@ietf.org] On Behalf Of Klaus Hartke
> Sent: Wednesday, July 18, 2018 10:00 AM
> To: consultancy@vanderstok.org; Core <core@ietf.org>
> Subject: Re: [core] ue of resource type in collections
> 
> 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], 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
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core