[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] question on singletons
In doing some additional exploration of corner cases for signatures, I came up with the following scenario:
1] a graph contains the singleton: =example<#email>&/&/“me@example.biz”2] time passes, and the subject needs to add a new, additional, email to the graph: “me@example.org”
what i assume will transpire is:
1] delete the singleton =example<#email>&/&/“me@example.biz”2] create a new email collection:=example[<#email>]<@0>&/&/“me@example.biz”=example[<#email>]<@1>&/&/“me@example.org”
how does an XDI service know ahead of time this is what needs to be done, or is that somehow automatically handled by the graph server? if the former, what happens if the client does not have a $get policy, but does have a $set policy in place?
this means (among other cascading consequences), that if a signature/encryption was present on the original singleton, a new signature/encryption values need to be generated for one or both of the new triples.
=peterd
Distinguished Engineer, Director, Neustar FoundryPeter Davis: Neustar, Inc.45980 Center Oak Plaza Sterling, VA 20166[T] +1 571 434 5516 [E] peter.davis@neustar.biz [W] http://www.neustar.biz/ [X] xri://@neustar*pdavis [X] xri://=peterdThe information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]