1 / 12

Designing For Privacy Safe Data Sharing, via Semantic Web Architecture (a sketch)

Sandro Hawke, W3C October 17, 2008 – Santa Clara, CA. Designing For Privacy Safe Data Sharing, via Semantic Web Architecture (a sketch). W3C (Web Standards) ‏. Helping create industry standards ~50 WGs, ~500 participants, ~50 staff HTML, CSS, XML (etc), SOAP, P3P

niloufer-fayaz
Download Presentation

Designing For Privacy Safe Data Sharing, via Semantic Web Architecture (a sketch)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sandro Hawke, W3C October 17, 2008 – Santa Clara, CA Designing For PrivacySafe Data Sharing, via Semantic Web Architecture(a sketch)

  2. W3C (Web Standards)‏ • Helping create industry standards • ~50 WGs, ~500 participants, ~50 staff • HTML, CSS, XML (etc), SOAP, P3P • RDF, OWL, SPARQL, GRDDL, RIF • “Semantic Web”, “Linked Data” • ... so much more to do!

  3. Data Sharing: Business Risks (Opportunities) • amazing possibilities • amazing dangers • we need a solid approach • the Web gives us a good model

  4. So Much Information • Imagine what your cell phone could know: • it hears everything going on around you • it knows where you are • it knows the motion of your body • it sees what's in front of it • it knows your contacts • it hears your phone calls

  5. What Could We Do With It? • ... I'm not even going to try to guess. • (but I know it'll be wild)‏

  6. Requirements: No Surprises • A clear, robust, simple-as-possible model • Based on consensus rights and responsibilities • Make everything predictable for all parties • No Risk? No. But like a normal business venture.

  7. Suggestion: Leverage the Web • Information origin == web server • Shared control by originating parties • if the information originates from a transaction, all parties ought to have a prior arrangement about control

  8. Example: My-Location Website • Websites provide information • Your cell phone has lots and lots =

  9. Example: Phone-Location Website • Different pages (APIs) for different uses: • Raw data, current and past • Geocoding, On-Map, Various Merges • “blurred” (eg only city information)‏ • purpose-centric (eg location when I'm on the job)‏ • HTML, RDF, XML, whatever

  10. Grant Access to Person • List the specific people (agents) for access to specific pages • spouse – full location access • fellow-traveler during trip – full location access • child – city access

  11. Grant Access by Filter • Roles • co-worker • “friend” in social network • Location • friends near me • etc....

  12. Access for a Purpose • cc-non-commercial • HIPPA "we may disclose your health information to a healthcare provider who is providing treatment to you" • Law Enforcement (automating what court orders allow)‏

More Related