![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Mary, I do not think that Jurisdiction and
Postal need to be the same, often they are not the same, since postal rarely
follows the same “boundaries” as jurisdictional. Since they may, or
may not, be the same is the reason they are both included. You can not assume
they are the same. Marc B Marc Berryman, ENP From: Mary Barnes
[mailto:mary.barnes at nortel.com] Hi
all, This
thread never seemed to conclude with clear consensus as to whether folks see a
need for both these specific location types rather than being able to use a
common "civic" locationType. I went back
through the threads and the majority of the responses indicated that both of
the values should be the same (with And,
just to be precise, we're proposing changing locationType from a set of {any,
civic, geodetic, postalCivic, jurisdictionalCivic, locationURI} to a set of {any,
civic, geodetic, locationURI}. Regards,
|
_______________________________________________ Geopriv mailing list Geopriv at ietf.org https://www1.ietf.org/mailman/listinfo/geopriv