On Sun, Jul 7, 2013 at 6:40 AM, Ben Niven-Jenkins <[email protected]>wrote:
> Rich, > > On 4 Jul 2013, at 07:29, Richard Alimi wrote: > > On Mon, Jul 1, 2013 at 11:37 PM, Ben Niven-Jenkins < > [email protected]> wrote: > >> On 1 Jul 2013, at 19:34, Y. Richard Yang wrote: > >> So it will be an item defined in "meta" of the IRD. Similar to current > "cost-types", which defines mapping of names to cost types, this mapping > will be from network map name/ID to URI. Is this what you have in mind? > > > > Basically, yes. > > > > I was thinking something simpler (without the need for another lookup > table) - for each resource entry, we just add an 'id' attribute. > > Just to confirm. The ID is for the resource, not the dependent resource. I feel that this is more consistent. > I think we're saying the same thing (when I replied to Richard I was > working from memory and forget "meta" applies to the whole IRD), what I'm > thinking is that an existing entry of: > > "resources" : [ > { > "uri" : "http://alto.example.com/networkmap";, > "media-type" : "application/alto-networkmap+json" > }, { > "uri" : "http://alto.example.com/costmap/num/routingcost";, > "media-type" : "application/alto-costmap+json", > "capabilities" : { > "cost-type-names" : [ "num-routing" ] > } > }] > > would become: > > "resources" : [ > { > "uri" : "http://alto.example.com/networkmap";, > "media-type" : "application/alto-networkmap+json", > "id" : "default-map" > }, { > "uri" : "http://alto.example.com/costmap/num/routingcost";, > "media-type" : "application/alto-costmap+json", > "id" : "default-map", > If we make the consistent usage that each resource has an id, then the line right above will be: "id": "default-costmap" Overall, I support that we add an "id" field for each resource entry. I would also like to add a "uses" attribute, just as a software package system will do. Hence, the preceding example becomes: "resources" : [ { "uri" : "http://alto.example.com/networkmap";, "media-type" : "application/alto-networkmap+json", "id" : "default-networkmap" }, { "uri" : "http://alto.example.com/costmap/num/routingcost";, "media-type" : "application/alto-costmap+json", "id" : "default-costmap", "uses": ["default-map"] "capabilities" : { "cost-type-names" : [ "num-routing" ] } }] For the content of each individual resource, we include both the id and version tag, as Rich's earlier proposal. In other words, now costmap can also have version tags. The use case that I am thinking is that applications can build on top of cost maps, and hence can know if the cost map has changed from the previous version fetched. Richard > "capabilities" : { > "cost-type-names" : [ "num-routing" ] > } > }] > > Which I think is the same as what you are suggesting. > > Ben > >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
