Richard On 9 Jul 2013, at 22:48, "Y. Richard Yang" <[email protected]> wrote: > >> Introducing an identifier for each resource may make the entries look more >> "consistent" but it's not clear to me how (or whether) they'd be used. If >> folks think it's worthwhile I won't object but keeping things simple helps >> keep the usage clear. > > One usage that I have in mind is that later, when we build up more services, > for example, on top of cost map, then the application or higher-level service > can use the costmap id to identify the costmap that serves as the base. > > More specifically, one item that I am working on is topology service and even > make ALTO as a base for actions. For example, an app fetches a topology, and > computes a route. When the app submits the request to instantiate the route, > the app should identify the map used (by using both id and vtag) so that the > network can retrieve the corresponding topology.
The app may need to identify the map used but why does it need to identify the cost map separately to the network map? Ben > > > At this moment, we can take down the path of allowing every resource entry > with an id, but if an id is not used, it may not need to appear. How does > this sound? > > Richard
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
