One clarification to this. Along with this change, in order to retain the ability for an ALTO Server referring to a set of resources in another IRD, we would also like to allow an IRD entry to point directly to another iRD. This would basically mean that there would be entries specifying the media type of "application/alto-directory+json". Without this, it would force an ALTO Server to explicitly list all resources at the other server, and we thought that would be coupling them too tightly.
Thanks, Rich On Tue, May 14, 2013 at 9:24 AM, Richard Alimi <[email protected]> wrote: > When we started specifying the format of the Information Resource > Directory (IRD), one concern was the overall size. As such, we designed > mechanisms to allowed a single entry in the IRD to specify that it could > handle multiple media types (both in the request and could provide > multiple media types). Based on some recent (off-list) discussions with > Wendy, this may be less of a concern and we may want to go for simplicity. > > Here's an example of one entry we have now: > > { > "uri" : "http://custom.alto.example.com/maps";, > "media-types" : [ > "application/alto-networkmap+json", > "application/alto-costmap+json" > ], > "accepts" : [ > "application/alto-networkmapfilter+json", > "application/alto-costmapfilter+json" > ] > } > > > The proposal is to have each entry declare exactly one media-type for the > response, and either 0 or 1 media types for the request (e.g., the > unfiltered cost map doesn't need anything in the request - it's a simple > GET). > > Here's what the corresponding entry from above would look like: > > { > "uri" : "http://custom.alto.example.com/maps";, > "media-type" : "application/alto-networkmap+json", > "accepts" : "application/alto-networkmapfilter+json", > }, { > > "uri" : "http://custom.alto.example.com/maps";, > "media-types" : "application/alto-costmap+json", > "accepts" : "application/alto-costmapfilter+json", > } > > > > The editors think this is a reasonable change to make. Comments are very > welcome. > > Since we are on a tight schedule here, if we don't hear anything within > the next week (by May 21st), we will make the corresponding changes to the > draft. > > Thanks! > Rich > >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
