>> > What is the location object be are all talking about ? XML?
>> > ASN.1 <just
>> > kidding>
...
>geopriv presumably is a discussion of two distinct issues physical
>location and privacy..so it stands to reason that the object under
>discussion may have two distinct features ..A. a semantical representation
>of physical location and a separate but distinct privacy object that
>describes the privacy policy to be used in association with the location
>object.
...
>either linked to or imbedded in the object. I need to re read some of the
>W3C work on P3P to see is there is something that can be snarfed up and reused.
>
>http://www.w3.org/P3P/
I'm tuning in late. If Haitao Tang or Mari Korkea are here, "hi".
XML has an advantage, P3P offers a schema.
However, the motivation for the schema applied to non-DOM objects
(e.g., the http state mechanism, aka "cookies")
arose from a P3P-esque label scheme applied just to cookies, in the
now expired draft-jaye-http-trust-state-mgt-NN.txt.
Policies can be both P3P-esque, and processed simpler than wf or wf+v xml.
ASN.1 has an advantage, TSP (rfc3161) uses it. The PKI uses it. PGP uses it.
...
Location, State, and {data collection|privacy}
It isn't just where the end-point is (absolute or relative), but also when
it is. State is an interesting part of the problem.
The problem with decoupling location from privacy is that privacy either
is something fairly abstract and resembling a AAA statement about the
mobile computer system, or it is something jurisdictionally specific and
subject to change if the end-point's location is capable of proof. With
luck the first (mechanism) can express the second (policy).
I mention proof because it seems to me that that also is an interesting
part of the problem.
...
See draft-ietf-provreg-epp-06.txt for one go at snarf-and-reuse.
Other resources are the W3C's Mobile and P3P workshops:
http://www.w3.org/Mobile/posdep-workshop.html
http://www.w3.org/P3P/mobile-privacy-ws
Cheers,
Eric
Received on Sat Apr 6 14:08:51 2002
This archive was generated by hypermail 2.1.8 : Thu Jan 22 2004 - 12:32:23 EST