I submitted a position paper and gave a presentation noting that requirements that are simple to express can have large consequences in terms of complexity and implementation. I mentioned as an example to efforts in the Liberty Alliance to avoid correlation of identity across service providers through the use of opaque name identifiers. Another example is managing policy definitions with multiple parties involved in setting policy. I also highlighted the applicability of the FTC Do Not Track requirements mentioned in the previous W3C workshop on Web Tracking and User Privacy.
The workshop was well attended, including significant attendance and interest from a wide variety of stakeholders.
Possible next steps were focused on incremental improvements to current technology, with the intent of achieving results in a short time frame, including
(a) Creating a standard for tagging web form fields so that password fillers can work reliably (e.g. know which field is user name, password etc )
(c) further discussion of the broader issues on a mail list.
There was a useful review of requirements with rough agreement on most of these. Discussion of the failure of some earlier attempts at addressing these issues included mention that this is a wicked problem, that usability is essential, that it must be a decentralized and user-centric system and that the buy-in of all stakeholders, including web service providers is essential, and that there must be incentives for all.
Note was made of the relevance of the NSTIC (US National Strategy for Trusted Identities in Cyberspace) initiative.
There were many interesting papers, a small sampling is the following:
Federated Browser-Based Identity using Email Addresses, Mike Hanson Dan Mills Ben Adida
The Emerging JSON-Based Identity Protocol Suite, Michael B. Jones, also see the slides
(edited first paragraph to update link to workshop report and provide link to agenda with presentations)
rea·son·able – (see http://www.merriam-webster.com/ )
a : being in accordance with reason reasonable theory>
b : not extreme or excessive < reasonable requests>c : moderate, fair reasonable chance> reasonable price>d : inexpensive“
At the W3C workshop on Web Tracking and User Privacy there were a number of themes.
One theme is that there are different business interests related to tracking user activity on the web and different definitions of tracking. For example, 1st party tracking might involve a web site recording information to maintain a shopping cart contents, something a user would typically expect. Third party tracking might be used to provide advertisements to a user based on their activity. This may or may not be acceptable to a user but relates to efforts to fund a site that may provide value without charging a fee.
Some tracking offers end users value, whether it be in supporting “free” services or in providing targeted ads that are useful and of interest.
Of greater concern is the lack of transparency and accountability – tracking without user knowledge or permission and the potential for misuse of the information due to inappropriately long retention or
Another theme is that usability is important and this includes not burdening users with needless and numerous prompts for permission. In fact, given experience with security prompts such as those related to SSL/TLS certificates,
In case you are not aware of it, the OASIS IDTrust Member Section has a collection of good links to introductions and other information related to PKI, take a look at http://www.oasis-pki.org/resources .