The intention was for a location node to be required if the <geo-location> container was present. Apparently this will only work if "container geo-lcoation" is a presence container. I'm not even sure that's all that smart of a requirement (e.g., maybe someone just wants to indicate the reference-frame for an object). I'll remove the mandatory from location.
Thanks, Chris. > On Jul 11, 2019, at 9:54 AM, Jan Kundrát <[email protected]> wrote: > >> The "location" choice is defined as mandatory, so an instance of one of the >> cases must be present. I don't know whether it is necessary or not, but you >> can avoid it easily by overriding the definition: > > Thanks for explaining this. I'll leave it to the draft authors to evaluate > whether an optional geolocation makes more sense than a hard-coded one. > > Diky > Honza K. > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
