Re: The PII Namespace

Hi Gannon

You'll what now?? :)

I know PII has been discussed before, expecially in view of a 
comparative implementation to FOAF.

Your point in this might be better explained if you could provide a 
practical example - how could PII (or FOAF for that matter - both seek 
to achieve the same thing) assist an agency in reinforcing a stated 
privacy policy? Privacy is a bit of a big ticket eGov item for many 
states/agencies world wide at the moment, so I for one would be curious 
as to your thoughts there. :)

(Remember to keep it simple - it may have to be explained this to 
"policy wonks".)

Chris

On 7/03/2011 11:28 AM, Gannon Dick wrote:
> Site searches normally require a "bit bucket" of sorts when search results have some cyber-stalking overtones.  From a Commercial Perspective most Social Networking sites and Search Engines can push an extra page of ads, so the trouble of rewriting this page functionality is perhaps worthwhile.
>
> For Government and non-profit NGO's the situation is different.  There is no potential benefit to a sticky domain.  Rather than go to the trouble of explaining that the query is out of line, users can be sent to the Personally Identifiable Information (PII) namespace.
>
> http://purl.org/pii/terms/  There are 15 terms/URL's, for the fastidious, but any one of them will make the point that the requested information is unavailable.  In addition, a 16th, http://purl.org/pii/terms/misc should be reserved for exactly the opposite message - that the referring page contains no PII.  That may be an adoptable standard, maybe not.  It might be handy for reinforcement of a stated privacy policy.  This is not so much about creating Standards as it is saving time and trouble on Requirements Documentation, which is to say I'll let Chris Beer handle the Internationalization :o)
>
> --Gannon

Received on Monday, 7 March 2011 23:30:18 UTC