<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Many people have already set-up things to establish privacy, in
various ways and some more effective than others. Multiple AS might
be one of them.<br>
<br>
For example, if I were enrolled in an HIV-positive clinical study, I
might want the study's AS to contain my authorization just for
access to the relevant RSs and not be noted in my clinical record.
The very fact of being enrolled in the study is too much of a
disclosure.<br>
<br>
Similarly, a person who has established a social networking account
on an adult-interest web site might want to keep that out of sight
from others. The mere existence of such privacy preferences in a
common authorization resource might raise uncomfortable questions if
they were revealed. One solution is to have a distinct AS for the
adult-interest site. That can be generalized.<br>
<br>
For privacy reasons, I give every one of my on-line vendor contacts
a unique e-mail address to contact me, e.g., <i>vendor.com</i>@glenmarshall.com
Even though all the e-mail comes to a common account for me to read,
it makes it impossible for unrelated vendors to assemble and share a
dossier keyed by e-mail. Each vendor has my privacy and contact
preferences relative to just cou common business. With a large
number of e-mail addresses I also avoid common identification
services, e.g., OAuth, except where it suits my purposes. A
side-effect is that I do not need complex trust relationships among
vendors. This is not much of a schlep for me, once it was set-up.
<br>
<br>
... and so on. <br>
<br>
<div class="moz-signature">
<p><b>Glen F. Marshall</b><br>
Consultant<br>
Security Risk Solutions, Inc.<br>
698 Fishermans Bend<br>
Mount Pleasant, SC 29464<br>
Tel: (610) 644-2452<br>
Mobile: (610) 613-3084<br>
<a class="moz-txt-link-abbreviated" href="mailto:gfm@securityrs.com">gfm@securityrs.com</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.SecurityRiskSolutions.com">www.SecurityRiskSolutions.com</a></p>
</div>
<div class="moz-cite-prefix">On 12/15/15 15:10, Debbie Bucci wrote:<br>
</div>
<blockquote
cite="mid:CAG6zQ1aiY5AQ=zmAdqhzez6pi4UVL0-uiGJ+HZj3-Otr9DCB7Q@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">
<div>Yes I believe ...<font color="#1f497d" size="3"
face="Calibri">some poor schlep is going to be on the hook
for keeping his AS replicated with the one I designated
because of “Policy”</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri">AND
(ideally) </font></div>
<div><br>
</div>
<div><font color="#1f497d" size="3" face="Calibri">The
trusted application that you are familiar designate (Bill's
source of truth) would/should trigger/drive the updates. </font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri">Perhaps a
schlep provide UI to verify update and changes (and trigger
receipts of those update) - would be considered a
safeguard.</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri">Given your
experience with PHRs - you know best - there maybe one
source of truth for Healthcare data today but with IOT and
other yet to be determined innovations - I still believe
(under the covers) it will be distributed in nature.</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri">Understanding
that going in may impact some of our decisions. </font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
<div><font color="#1f497d" size="3" face="Calibri"><br>
</font></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-heart mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-heart">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a>
</pre>
</blockquote>
<br>
</body>
</html>