On 2016-03-04 00:47, Rob Shakir wrote:
> Yes. Any identity value that extends that base must be unique AIUI, so each
> of those values then defines its namespace. Why do we carry it in the JSON?
The identity values must indeed be unique - and that's precisely why
they need module/namespace qualification. In the example below, a:x and
b:x are valid and different values for the leaf y. Obviously a more
realistic example would have two modules defining "conflicting"
identities with a base defined in a third module - i.e. this logic makes
it possible for "independent parties" to define unique identities with a
common base, without the need for having a "global registry".
--Per Hedeland
module a {
namespace urn:a;
prefix a;
identity id;
identity x {
base id;
}
}
module b {
namespace urn:b;
prefix b;
import a {
prefix a;
}
identity x {
base a:id;
}
leaf y {
type identityref {
base a:id;
}
}
}
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
