Hi Wendy,
To clarify, you mean the assigned name in IRD. For example, in the example
below, it is "num-routing", "num-hop", right?
HTTP/1.1 200 OK
Content-Length: 2333
Content-Type: application/alto-directory+json
{
"meta" : {
"cost-types": {
"num-routing": {
"cost-mode" : "numerical",
"cost-metric": "routingcost",
"description": "My default"
},
"num-hop": {
"cost-mode" : "numerical",
"cost-metric": "hopcount"
},
"ord-routing": {
"cost-mode" : "ordinal",
"cost-metric": "routingcost"
},
"ord-hop": {
"cost-mode" : "ordinal",
"cost-metric": "hopcount"
}
},
The related definition then is
object-map {
JSONString -> CostType;
} IRDMetaCostTypes;
object {
JSONString cost-type-names<1..1>;
} CostMapCapabilities;
The proposal is to limit JSONString? I agree that this is more consistent
with PIDName, Resource ID, ... We restricted PIDName and Resource ID with
an intention of introducing hierarchy in the future (e.g., this is why '.'
is not allowed ...) Is this necessary for CostType names?
Thanks!
Richard
On Thu, Mar 20, 2014 at 9:54 AM, Wendy Roome <[email protected]>wrote:
> Folks,
>
> We were careful to spell out the length and character set restrictions on
> cost-metrics, PID names, and so on. But unless I missed it, we didn¹t put
> any restrictions on cost-type names. I think the natural place for that
> would be {10.7}.
>
> Are the restrictions listed somewhere else and I missed them?
>
> If not, should we say that cost-type names must follow the same rules as
> resource-ids, as defined in {10.2}?
>
> Yes, I know it¹s too late to change the official document; I assume this
> is a candidate for the errata sheet.
>
> - Wendy Roome
>
>
> _______________________________________________
> alto mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=====================================
| Y. Richard Yang <[email protected]> |
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/ |
=====================================
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
