BEGIN:VCALENDAR VERSION:2.0 PRODID:-//hacksw/handcal//NONSGML v1.0//EN METHOD:PUBLISH BEGIN:VEVENT DTSTAMP:20240319T125350Z DESCRIPTION:Click for Latest Location Information: http://graphorum2019.dat aversity.net/sessionPop.cfm?confid=132&proposalid=11022\n
The main differ
ence between an Information System and a Knowledge System is the appropriat
e application of context. We strive to put the right data in the right hand
s at the right time. This ends up helping people make informed decisions be
cause they have appropriate, filtered, prioritized data shaped by the conte
xt of their inquiry. It is simultaneously more flexible and less of a burde
n on the person asking the question.
\n
\nAPIs can benefit
knowing about who is asking for what where personalization meets domain kno
wledge. The flip side of context is a defensive one. Who is asking for what
in what context? APIs that assume flat or nonexistent contexts are often e
xploitable through privilege escalation and other attacks.
This tal k will pitch a vision and show running code that allows you to manage the i ntersection of convenience and security by applying context to your APIs. Y ou will hear about how facts themselves can be filtered based upon how they were learned and what use they are being given. This is crucial in any mod ern environment that has regulatory, government classification, customer pr ivacy or other needs around how data is shared.
\n DTSTART:20191016T113000 SUMMARY:API Context: Who Is Asking for What of Our Graphs? DTEND:20191016T122959 LOCATION: See Description END:VEVENT END:VCALENDAR