tag:blogger.com,1999:blog-12447072.post1294244257428374847..comments2024-02-13T08:56:52.521-05:00Comments on ConnectID: Consent Context Markup LanguagePaul Madsenhttp://www.blogger.com/profile/08489111023182783403noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-12447072.post-79284882714368242852007-04-30T14:41:00.000-04:002007-04-30T14:41:00.000-04:00Hi Gerald, I wasn't thinking of how the user's pre...Hi Gerald, I wasn't thinking of how the user's prefs are captured, reconciled, etc, XACML could well serve for that. Rather I was imagining a syntax for capturing the various permutations by which consent can be captured. So, descriptive as opposed to restrictive.Paul Madsenhttps://www.blogger.com/profile/08489111023182783403noreply@blogger.comtag:blogger.com,1999:blog-12447072.post-1688377592368580162007-04-30T12:31:00.000-04:002007-04-30T12:31:00.000-04:00Paul - One way to achieve this would be - as far a...Paul - <BR/>One way to achieve this would be - as far as I can see - by using the policy system in XACML. THis way the user could initially formulate a privacy policy which could then get matched to the SP policy. So for instance, the SP asks for Name, SSN, DOB - or - Name, SSN, Address - or - Name, Address, valid Credit Card number (order could indicate preference). The User policy might want toAnonymousnoreply@blogger.com