I'm confused. How is my UMA Authorization Server supposed to use the Privacy Policies and Terms of Service? Are we assuming some highly standardized data model around some 50 aspects of what Facebook might or might not do with my data before UMA can work? The degree of domain and business specificity that this approach implies seems totally impractical.
One of the Facebook documents and one of the Twitter documents are now in component form. On the Facebook doc, there are some names for section components, positing a taxonomy. These names (mostly verbs) are simply a guess, and non-exclusive (the same materials can be recombined using different names). But, IMHO, evocative. In any event, a starting point.Both docs live in this tree:A theory of such trees is at:On Tue, Sep 29, 2015 at 5:03 AM, Eve Maler <eve@xmlgrrl.com> wrote:I started collecting a few of these here:
https://github.com/KantaraInitiative/wg-uma/wiki/UMA-Legal:-Examples-of-Terms-and-Conditions-for-Acquiring-Social-IdP-OAuth-Client-Credentials
Eve Maler | cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl | Calendar: xmlgrrl@gmail.com
_______________________________________________
WG-UMA mailing list
WG-UMA@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma