[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] NRI link contract use case (was RE: [xdi] Agenda: XDI TCTelecon Thursday 1-2PM PT 2008-07-10)
--Apple-Mail-385--351913207
Content-Type: multipart/alternative;
boundary=Apple-Mail-384--351913273
--Apple-Mail-384--351913273
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
Hi Tatsuki,
You may be thinking of the XDI-ATI link contracts that work that way.
The XDI-RDF ones are still a bit of a work in progress.
=jbradley
On 17-Jul-08, at 1:02 PM, Tatsuki Sakushima wrote:
> Hi Marcus,
>
> > Hmm correct me if I'm wrong, but I think it would make sense to
> > distinguish between a link contract and a template. Because it seems
> > that in TX the RP can specify "optional" and "required"
> attributes, and
> > then the OP makes the decision which attributes are actually
> exchanged.
>
> Yes. If this is the case, distinguishing between a link contract and
> a template is required. But my assumption of how OP behaved was that
> OP just made decision if it accepted a link contract proposal(a
> template) from RP. No modification in the contract by OP occurs. I
> was not sure this part, so I want to ask Nat first.
>
> Also, my impression of the current basic pattern was that it focuses
> on *authorization*. My image of Link contract was something more
> like *mutual agreement process or handshaking* for a specific
> contract context. So signing from both parties(OP/RP) probably is
> required. RDFs related to authorizatoin may be one of contexts that
> a Link Contract handles but may not be a Link Contract itself. I
> thought that XDI signature would be a part of Link contract. I
> missed the 7/3 telecon. Sorry if you have talked about it already. I
> am very interested to see how XDI signature works in Link contract.
>
> Regards,
> Tatsuki
>
> Tatsuki Sakushima
> NRI Pacific - Nomura Research Institute America, Inc.
> TEL:(650)638-7258
> SkypeIn:(650)209-4811
>
> Markus Sabadello ????????:
>> Hmm correct me if I'm wrong, but I think it would make sense to
>> distinguish between a link contract and a template. Because it
>> seems that in TX the RP can specify "optional" and "required"
>> attributes, and then the OP makes the decision which attributes are
>> actually exchanged.
>> But maybe I am wrong.
>> Anyway, I played with my Visio file a bit again, trying to adapt it
>> to the new link contract pattern at http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern
>> Find attached a new version. Maybe it would be better to put it on
>> a wiki page, but I liked the idea of color coding the equivalent
>> parts of the link contracts and the XML examples at http://wiki.openid.net/Trusted_Data_Exchange
>> .
>> Note to Drummond:
>> - I used predicates $get$req and $get$opt for required/optional
>> attributes. Maybe you have a better idea to express that.
>> Markus
>> On Thu, Jul 17, 2008 at 7:20 PM, Tatsuki Sakushima <tatsuki@nri.com
>> <mailto:tatsuki@nri.com>> wrote:
>> Hi Drummond,
>> Thank you for replying. I missed a chance to talk with Nat the
>> last
>> week because he was out of country. Today I have a telecon with
>> Nat,
>> I'll explain to him about the basic pattern that the TC discussed.
>> Hopefully we firm up our idea about TX and Link Contract while you
>> are in vacation ;-)
>> Have nice vacation and see you in six weeks. Maybe DIDW in
>> September
>> is a good chance to have a discussion face-to-face?
>> Best,
>> Tatsuki
>> Tatsuki Sakushima
>> NRI Pacific - Nomura Research Institute America, Inc.
>> TEL:(650)638-7258
>> SkypeIn:(650)209-4811
>> Drummond Reed ????????:
>> Tatsuki,
>> Sorry for the delay in replying to this -- I'm getting ready
>> to
>> go on
>> vacation and trying to catch up with past mail.
>> I think that the link contract pattern we discussed last week
>> can work for
>> an OP-defined contract per your requirements. We should make
>> that an example
>> use case we document on the wiki.
>> I'd be happy to help work on this once I am back from
>> sabbatical
>> (six
>> weeks).
>> Best,
>> =Drummond
>> -----Original Message-----
>> From: Tatsuki Sakushima [mailto:tatsuki@nri.com
>> <mailto:tatsuki@nri.com>]
>> Sent: Thursday, July 10, 2008 3:56 PM
>> To: Markus Sabadello
>> Cc: Drummond Reed; xdi@lists.oasis-open.org
>> <mailto:xdi@lists.oasis-open.org>; Sakimura, Nat
>> Subject: Re: [xdi] Agenda: XDI TC Telecon Thursday 1-2PM
>> PT
>> 2008-07-10
>> Hi Markus,
>> Thank you for considering the TX use case.
>> Probably I should confirm with Nat first, but let me
>> clarify
>> a few
>> points in the TX spec.
>> 1) In the TX spec, a template means user data(which is a
>> OpenID owner's
>> information) handling policy proposal *without signature*
>> from RP.
>> We might not have to distinguish a link contract or a
>> template.
>> If it is signed, it is a contract. If not, it's a
>> template.
>> Let me confirm it with Nat.
>> 2) In the TX, a contract proposal comes from RP because it
>> is a data
>> usage policy that RP must commit. In the basic pattern the
>> we talked
>> about today, OP should define a link contract. We might
>> have
>> to find
>> another way to do this in the TX spec side if following
>> the
>> basic
>> pattern or consider a different pattern from the basic one
>> in the link
>> contract pattern side.
>> I think Nat is in Sweden today. I hope he read this and
>> reply soon.
>> Tatsuki
>> Tatsuki Sakushima
>> NRI Pacific - Nomura Research Institute America, Inc.
>> TEL:(650)638-7258
>> SkypeIn:(650)209-4811
>> Markus Sabadello ????????:
>> I think what's missing on the LinkContractPattern page
>> is an example for
>> a "link contract template". Or is that concept
>> deprecated now?
>> I'm asking because I was thinking about how to
>> update my
>> proposal for
>> how link contracts in Nat's OpenID Trusted Data
>> Exchange
>> would look
>> like:
>> http://www.oasis-
>> open.org/apps/org/workgroup/xdi/document.php?
>> document_id=28380
>> <http://open.org/apps/org/workgroup/xdi/document.php?document_id=28380
>> >
>> Maybe such a template ("Bob REQUESTS permission to
>> access some
>> attribute") could look like this:
>> $$$contract <-- this indicates a link contract
>> TEMPLATE, i.e. a
>> request for something -->
>> $is$a
>> $contract
>> $a$contract
>> =!2222 <-- Bob is the one who
>> requests a
>> link contract
>> -->
>> $get
>> /
>> $$
>> $add
>> /
>> $$
>> +y
>> +z
>> $mod
>> /
>> $$
>> +x
>> +y
>> +z
>> $del
>> /
>> $$
>> +x
>> +y
>> +z
>> Then the answer to that request (i.e. the
>> "instantiated"
>> link contract)
>> with actual permissions given by Alice to Bob would be
>> exactly this:
>> http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern#head-
>> 7b714236b726216c5aec36b9ceafdcdf7de1961b
>> Markus
>> On Thu, Jul 10, 2008 at 10:04 AM, Drummond Reed
>> <drummond.reed@cordance.net
>> <mailto:drummond.reed@cordance.net>
>> <mailto:drummond.reed@cordance.net
>> <mailto:drummond.reed@cordance.net>>> wrote:
>> Following is the agenda for the unofficial
>> telecon of
>> the XDI TC at:
>> Date: Thursday, 10 July 2008 USA
>> Time: 1:00PM - 2:00PM Pacific Time
>> TO ACCESS THE AUDIO CONFERENCE:
>> Dial In Number: 571-434-5750
>> Conference ID: 3526
>> AGENDA
>> 1) STANDING RULE BALLOT
>> TC Administrator Mary McRae has suggested we have a
>> ballot on the
>> following
>> Standing Rule in order to formalize our informal
>> meeting schedule:
>> "Standing Rule: Does the TC wish to adopt a
>> standing rule to
>> conduct
>> regular business only by electronic ballot, without
>> Meetings, with
>> the
>> exception of Meetings called for a special purpose
>> with a minimum of
>> 15
>> calendar days notice?"
>> 2) XDI RDF LINK CONTRACT BASIC PATTERN
>> Our tech topic for the day is a very core one:
>> confirming the basic
>> pattern
>> of XDI link contracts in the XDI RDF model. This
>> has
>> been assigned
>> Issue #4
>> on and a proposal written up at:
>> http://wiki.oasis-
>> open.org/xdi/XdiOneIssues/LinkContractPattern
>> <http://open.org/xdi/XdiOneIssues/LinkContractPattern>
>> 3) SUMMER CALL SCHEDULE
>> We'll discuss summer vacation schedules and if/how
>> often we want to
>> have
>> calls over July/August.
>> 4) OTHER BUSINESS
>>
>> --------------------------------------------------------------------
>> -
>> To unsubscribe from this mail list, you must leave
>> the OASIS TC that
>> generates this mail. Follow this link to all your
>> TCs in OASIS at:
>> https://www.oasis-
>> open.org/apps/org/workgroup/portal/my_workgroups.php
>> <http://open.org/apps/org/workgroup/portal/my_workgroups.php
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS
>> TC that
>> generates this mail. Follow this link to all your TCs in
>> OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC
>> that
>> generates this mail. Follow this link to all your TCs in OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--Apple-Mail-384--351913273
Content-Type: text/html;
charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi =
Tatsuki,<div><br></div><div>You may be thinking of the XDI-ATI link =
contracts that work that way. </div><div><br></div><div>The XDI-RDF =
ones are still a bit of a work in =
progress.</div><div><br></div><div>=3Djbradley</div><div><br><div><div>On =
17-Jul-08, at 1:02 PM, Tatsuki Sakushima wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi =
Marcus,<br><br>> Hmm correct me if I'm wrong, but I think it would make =
sense to<br>> distinguish between a link contract and a template. =
Because it seems<br>> that in TX the RP can specify "optional" and =
"required" attributes, and<br>> then the OP makes the decision which =
attributes are actually exchanged.<br><br>Yes. If this is the case, =
distinguishing between a link contract and a template is required. But =
my assumption of how OP behaved was that OP just made decision if it =
accepted a link contract proposal(a template) from RP. No modification =
in the contract by OP occurs. I was not sure this part, so I want to ask =
Nat first.<br><br>Also, my impression of the current basic pattern was =
that it focuses on *authorization*. My image of Link contract was =
something more like *mutual agreement process or handshaking* for a =
specific contract context. So signing from both parties(OP/RP) probably =
is required. RDFs related to authorizatoin may be one of contexts that a =
Link Contract handles but may not be a Link Contract itself. I thought =
that XDI signature would be a part of Link contract. I missed the 7/3 =
telecon. Sorry if you have talked about it already. I am very interested =
to see how XDI signature works in Link =
contract.<br><br>Regards,<br>Tatsuki<br><br>Tatsuki Sakushima<br>NRI =
Pacific - Nomura Research Institute America, =
Inc.<br>TEL:(650)638-7258<br>SkypeIn:(650)209-4811<br><br>Markus =
Sabadello ????????:<br><blockquote type=3D"cite">Hmm correct me if I'm =
wrong, but I think it would make sense to distinguish between a link =
contract and a template. Because it seems that in TX the RP can specify =
"optional" and "required" attributes, and then the OP makes the decision =
which attributes are actually exchanged.<br></blockquote><blockquote =
type=3D"cite">But maybe I am wrong.<br></blockquote><blockquote =
type=3D"cite">Anyway, I played with my Visio file a bit again, trying to =
adapt it to the new link contract pattern at <a =
href=3D"http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern";>h=
ttp://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern</a><br></bl=
ockquote><blockquote type=3D"cite">Find attached a new version. Maybe it =
would be better to put it on a wiki page, but I liked the idea of color =
coding the equivalent parts of the link contracts and the XML examples =
at <a =
href=3D"http://wiki.openid.net/Trusted_Data_Exchange";>http://wiki.openid.n=
et/Trusted_Data_Exchange</a>.<br></blockquote><blockquote =
type=3D"cite">Note to Drummond:<br></blockquote><blockquote =
type=3D"cite">- I used predicates $get$req and $get$opt for =
required/optional attributes. Maybe you have a better idea to express =
that.<br></blockquote><blockquote =
type=3D"cite">Markus<br></blockquote><blockquote type=3D"cite">On Thu, =
Jul 17, 2008 at 7:20 PM, Tatsuki Sakushima <<a =
href=3D"mailto:tatsuki@nri.com";>tatsuki@nri.com</a> <<a =
href=3D"mailto:tatsuki@nri.com";>mailto:tatsuki@nri.com</a>>> =
wrote:<br></blockquote><blockquote type=3D"cite"> Hi =
Drummond,<br></blockquote><blockquote type=3D"cite"> =
Thank you for replying. I missed a chance to talk with =
Nat the last<br></blockquote><blockquote type=3D"cite"> =
week because he was out of country. Today I have a =
telecon with Nat,<br></blockquote><blockquote type=3D"cite"> =
I'll explain to him about the basic pattern that the =
TC discussed.<br></blockquote><blockquote type=3D"cite"> =
Hopefully we firm up our idea about TX and Link =
Contract while you<br></blockquote><blockquote type=3D"cite"> =
are in vacation ;-)<br></blockquote><blockquote =
type=3D"cite"> Have nice vacation and see you in six =
weeks. Maybe DIDW in September<br></blockquote><blockquote type=3D"cite"> =
is a good chance to have a discussion =
face-to-face?<br></blockquote><blockquote type=3D"cite"> =
Best,<br></blockquote><blockquote type=3D"cite"> =
Tatsuki<br></blockquote><blockquote type=3D"cite"> =
Tatsuki Sakushima<br></blockquote><blockquote =
type=3D"cite"> NRI Pacific - Nomura Research Institute =
America, Inc.<br></blockquote><blockquote type=3D"cite"> =
TEL:(650)638-7258<br></blockquote><blockquote =
type=3D"cite"> =
SkypeIn:(650)209-4811<br></blockquote><blockquote =
type=3D"cite"> Drummond Reed =
????????:<br></blockquote><blockquote type=3D"cite"> =
Tatsuki,<br></blockquote><blockq=
uote type=3D"cite"> Sorry for =
the delay in replying to this -- I'm getting ready =
to<br></blockquote><blockquote type=3D"cite"> =
go =
on<br></blockquote><blockquote type=3D"cite"> =
vacation and trying to catch =
up with past mail.<br></blockquote><blockquote type=3D"cite"> =
I think that the link contract =
pattern we discussed last week<br></blockquote><blockquote type=3D"cite"> =
can work =
for<br></blockquote><blockquote type=3D"cite"> =
an OP-defined contract per =
your requirements. We should make<br></blockquote><blockquote =
type=3D"cite"> that an =
example<br></blockquote><blockquote type=3D"cite"> =
use case we document on the =
wiki.<br></blockquote><blockquote type=3D"cite"> =
I'd be happy to help work on =
this once I am back from sabbatical<br></blockquote><blockquote =
type=3D"cite"> =
(six<br></blockquote><blockquote=
type=3D"cite"> =
weeks).<br></blockquote><blockqu=
ote type=3D"cite"> =
Best,<br></blockquote><blockquot=
e type=3D"cite"> =
=3DDrummond<br></blockquote><blo=
ckquote type=3D"cite"> =
-----Ori=
ginal Message-----<br></blockquote><blockquote type=3D"cite"> =
From: =
Tatsuki Sakushima [<a =
href=3D"mailto:tatsuki@nri.com";>mailto:tatsuki@nri.com</a><br></blockquote=
><blockquote type=3D"cite"> =
<<a =
href=3D"mailto:tatsuki@nri.com";>mailto:tatsuki@nri.com</a>>]<br></blockquo=
te><blockquote type=3D"cite"> =
Sent: =
Thursday, July 10, 2008 3:56 PM<br></blockquote><blockquote type=3D"cite">=
To: =
Markus Sabadello<br></blockquote><blockquote type=3D"cite"> =
Cc: =
Drummond Reed; <a =
href=3D"mailto:xdi@lists.oasis-open.org";>xdi@lists.oasis-open.org</a><br><=
/blockquote><blockquote type=3D"cite"> =
<<a =
href=3D"mailto:xdi@lists.oasis-open.org";>mailto:xdi@lists.oasis-open.org</=
a>>; Sakimura, Nat<br></blockquote><blockquote type=3D"cite"> =
Subject:=
Re: [xdi] Agenda: XDI TC Telecon Thursday 1-2PM =
PT<br></blockquote><blockquote type=3D"cite"> =
2008-07-=
10<br></blockquote><blockquote type=3D"cite"> =
Hi =
Markus,<br></blockquote><blockquote type=3D"cite"> =
Thank =
you for considering the TX use case.<br></blockquote><blockquote =
type=3D"cite"> =
Probably=
I should confirm with Nat first, but let me =
clarify<br></blockquote><blockquote type=3D"cite"> =
a =
few<br></blockquote><blockquote type=3D"cite"> =
points =
in the TX spec.<br></blockquote><blockquote type=3D"cite"> =
1) In =
the TX spec, a template means user data(which is =
a<br></blockquote><blockquote type=3D"cite"> =
OpenID =
owner's<br></blockquote><blockquote type=3D"cite"> =
informat=
ion) handling policy proposal *without =
signature*<br></blockquote><blockquote type=3D"cite"> =
from =
RP.<br></blockquote><blockquote type=3D"cite"> =
We =
might not have to distinguish a link contract or a =
template.<br></blockquote><blockquote type=3D"cite"> =
If it =
is signed, it is a contract. If not, it's a =
template.<br></blockquote><blockquote type=3D"cite"> =
Let me =
confirm it with Nat.<br></blockquote><blockquote type=3D"cite"> =
2) In =
the TX, a contract proposal comes from RP because =
it<br></blockquote><blockquote type=3D"cite"> =
is a =
data<br></blockquote><blockquote type=3D"cite"> =
usage =
policy that RP must commit. In the basic pattern =
the<br></blockquote><blockquote type=3D"cite"> =
we =
talked<br></blockquote><blockquote type=3D"cite"> =
about =
today, OP should define a link contract. We might =
have<br></blockquote><blockquote type=3D"cite"> =
to =
find<br></blockquote><blockquote type=3D"cite"> =
another =
way to do this in the TX spec side if following =
the<br></blockquote><blockquote type=3D"cite"> =
basic<br=
></blockquote><blockquote type=3D"cite"> =
pattern =
or consider a different pattern from the basic =
one<br></blockquote><blockquote type=3D"cite"> =
in the =
link<br></blockquote><blockquote type=3D"cite"> =
contract=
pattern side.<br></blockquote><blockquote type=3D"cite"> =
I =
think Nat is in Sweden today. I hope he read this =
and<br></blockquote><blockquote type=3D"cite"> =
reply =
soon.<br></blockquote><blockquote type=3D"cite"> =
Tatsuki<=
br></blockquote><blockquote type=3D"cite"> =
Tatsuki =
Sakushima<br></blockquote><blockquote type=3D"cite"> =
NRI =
Pacific - Nomura Research Institute America, =
Inc.<br></blockquote><blockquote type=3D"cite"> =
TEL:(650=
)638-7258<br></blockquote><blockquote type=3D"cite"> =
SkypeIn:=
(650)209-4811<br></blockquote><blockquote type=3D"cite"> =
Markus =
Sabadello ????????:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; I think what's missing on the LinkContractPattern =
page<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; is an example for<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; a "link contract template". Or is that =
concept<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; deprecated now?<br></blockquote><blockquote type=3D"cite">=
=
&n=
bsp; I'm asking because I was thinking about how to update =
my<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; proposal for<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; how link contracts in Nat's OpenID Trusted Data =
Exchange<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; would look<br></blockquote><blockquote type=3D"cite"> =
like:<br=
></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <a =
href=3D"http://www.oasis";>http://www.oasis</a>-<br></blockquote><blockquot=
e type=3D"cite"> =
open.org=
/apps/org/workgroup/xdi/document.php?document_id=3D28380<br></blockquote><=
blockquote type=3D"cite"> =
<<a =
href=3D"http://open.org/apps/org/workgroup/xdi/document.php?document_id=3D=
28380">http://open.org/apps/org/workgroup/xdi/document.php?document_id=3D2=
8380</a>><br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Maybe such a template ("Bob REQUESTS permission =
to<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; access some<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; attribute") could look like =
this:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; $$$contract <-- this indicates a link =
contract<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; TEMPLATE, i.e. a<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; request for something --><br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; $is$a<br></block=
quote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; $contract<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; $a$contract<br><=
/blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =3D!2222 <-- Bob is the one who =
requests a<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; link contract<br></blockquote><blockquote type=3D"cite"> =
--><br><=
/blockquote><blockquote type=3D"cite"> =
&n=
bsp; $get<br></blockq=
uote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; /<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; &nbs=
p; =
$$<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; $add<br></blockq=
uote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; /<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; &nbs=
p; =
$$<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+y<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+z<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; $mod<br></blockq=
uote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; /<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; &nbs=
p; =
$$<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+x<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+y<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+z<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; $del<br></blockq=
uote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; /<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; &nbs=
p; =
$$<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+x<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+y<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; =
+z<br></blockquote><=
blockquote type=3D"cite"> =
&n=
bsp; Then the answer to that request (i.e. the =
"instantiated"<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; link contract)<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; with actual permissions given by Alice to Bob would =
be<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; exactly this:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <a =
href=3D"http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern#he=
ad-">http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern#head-=
</a><br></blockquote><blockquote type=3D"cite"> =
7b714236=
b726216c5aec36b9ceafdcdf7de1961b<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; Markus<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; On Thu, Jul 10, 2008 at 10:04 AM, Drummond =
Reed<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <<a =
href=3D"mailto:drummond.reed@cordance.net";>drummond.reed@cordance.net</a><=
br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <<a =
href=3D"mailto:drummond.reed@cordance.net";>mailto:drummond.reed@cordance.n=
et</a>><br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <<a =
href=3D"mailto:drummond.reed@cordance.net";>mailto:drummond.reed@cordance.n=
et</a><br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; <<a =
href=3D"mailto:drummond.reed@cordance.net";>mailto:drummond.reed@cordance.n=
et</a>>>> wrote:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Following is the agenda for the =
unofficial telecon of<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; the XDI TC at:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Date: Thursday, 10 July 2008 =
USA<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Time: 1:00PM - 2:00PM Pacific =
Time<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; TO ACCESS THE AUDIO =
CONFERENCE:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Dial In Number: =
571-434-5750<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Conference ID: =
3526<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; AGENDA<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; 1) STANDING RULE =
BALLOT<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; TC Administrator Mary McRae has =
suggested we have a<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; ballot on the<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; following<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; Standing Rule in order to formalize =
our informal<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; meeting schedule:<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; &nbs=
p;"Standing Rule: Does the TC wish to adopt =
a<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; standing rule to<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; conduct<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; regular business only by electronic =
ballot, without<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Meetings, with<br></blockquote><blockquote type=3D"cite"> =
the<br><=
/blockquote><blockquote type=3D"cite"> =
&n=
bsp; exception of Meetings called for a =
special purpose<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; with a minimum of<br></blockquote><blockquote =
type=3D"cite"> =
15<br></=
blockquote><blockquote type=3D"cite"> =
&n=
bsp; calendar days =
notice?"<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; 2) XDI RDF LINK CONTRACT BASIC =
PATTERN<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Our tech topic for the day is a very =
core one:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; confirming the basic<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; pattern<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; of XDI link contracts in the XDI RDF =
model. This has<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; been assigned<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; Issue #4<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; on and a proposal written up =
at:<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p;<a =
href=3D"http://wiki.oasis";>http://wiki.oasis</a>-<br></blockquote><blockqu=
ote type=3D"cite"> =
open.org=
/xdi/XdiOneIssues/LinkContractPattern<br></blockquote><blockquote =
type=3D"cite"> =
<<a =
href=3D"http://open.org/xdi/XdiOneIssues/LinkContractPattern";>http://open.=
org/xdi/XdiOneIssues/LinkContractPattern</a>><br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; 3) SUMMER CALL =
SCHEDULE<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; We'll discuss summer vacation =
schedules and if/how<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; often we want to<br></blockquote><blockquote =
type=3D"cite"> =
have<br>=
</blockquote><blockquote type=3D"cite"> =
&n=
bsp; calls over =
July/August.<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; 4) OTHER =
BUSINESS<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; &nbs=
p; ------------------------=
--------------------------------------------<br></blockquote><blockquote =
type=3D"cite"> =
-<br></b=
lockquote><blockquote type=3D"cite"> =
&n=
bsp; To unsubscribe from this mail list, =
you must leave<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; the OASIS TC that<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; generates this mail. Follow this =
link to all your<br></blockquote><blockquote type=3D"cite"> =
&n=
bsp; TCs in OASIS at:<br></blockquote><blockquote =
type=3D"cite"> =
&n=
bsp; <a =
href=3D"https://www.oasis-";>https://www.oasis-</a><br></blockquote><blockq=
uote type=3D"cite"> =
open.org=
/apps/org/workgroup/portal/my_workgroups.php<br></blockquote><blockquote =
type=3D"cite"> =
<<a =
href=3D"http://open.org/apps/org/workgroup/portal/my_workgroups.php";>http:=
//open.org/apps/org/workgroup/portal/my_workgroups.php</a>><br></blockquot=
e><blockquote type=3D"cite"> =
--------------------------------=
-------------------------------------<br></blockquote><blockquote =
type=3D"cite"> To unsubscribe =
from this mail list, you must leave the OASIS TC =
that<br></blockquote><blockquote type=3D"cite"> =
generates this mail. =
Follow this link to all your TCs in OASIS =
at:<br></blockquote><blockquote type=3D"cite"> =
<a =
href=3D"https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups=
.php">https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.p=
hp</a><br></blockquote><blockquote type=3D"cite"> =
--------------------------------------------------------=
-------------<br></blockquote><blockquote type=3D"cite"> =
To unsubscribe from this mail list, you must leave the =
OASIS TC that<br></blockquote><blockquote type=3D"cite"> =
generates this mail. Follow this link to all =
your TCs in OASIS at:<br></blockquote><blockquote type=3D"cite"> =
<a =
href=3D"https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups=
.php">https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.p=
hp</a><br></blockquote><br>-----------------------------------------------=
----------------------<br>To unsubscribe from this mail list, you must =
leave the OASIS TC that<br>generates this mail. Follow this link =
to all your TCs in OASIS at:<br><a =
href=3D"https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups=
.php">https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.p=
hp</a> <br></div></blockquote></div><br></div></body></html>=
--Apple-Mail-384--351913273--
--Apple-Mail-385--351913207
Content-Disposition: attachment;
filename=smime.p7s
Content-Type: application/pkcs7-signature;
name=smime.p7s
Content-Transfer-Encoding: base64
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGITCCAtow
ggJDoAMCAQICEE2TeuJWprpXkMqh1ISkswAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MTAyMjIwMzEwMVoXDTA4MTAyMTIwMzEw
MVowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0GCSqGSIb3DQEJARYQamJy
YWRsZXlAbWFjLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAM8iEfzV7DTQKqBc
qqx3ZYfq/PyiZJs5HEov8vnHG6eRv1YE6zp0DuPyIbKeNRlHYda+Wd0Ux7VGtroEzGlhgqUzj1Xi
MP9YN7b4qrQlyeTwA1vTuNGNl217ZgZ9gwrc2Agf0I5qNiYf4KDiWC573hLmTqBuG2zh63lUjFbW
lpNddY+7mGYRfBer3cQaayYf4lIz2IEtT4E2XQrseVp2pzuwM9QgLa0J6V8b8fJSXcSD/o8z+/oQ
2jmwfR+APh18EPU2oOJYyxE0riYCcsbJA4Ff+puvnP5ExiitqxkEVHobvNq2NbAd+d7Y+JQ4Rj9R
VqYXoBGvXxhXUUCpSzbrzYsCAwEAAaMtMCswGwYDVR0RBBQwEoEQamJyYWRsZXlAbWFjLmNvbTAM
BgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBAD/Ix3ZLWcsqfURljbMYCoCUZweW1PtfbO0v
JbxXyhBvsrlGpoZbJuoWoPIy5Q4KxypJ1A5he0JsysixLZCJySi1yiHQ78fZt2r0aDxMRY4PKukx
gPNr5gmb4hBAov095Evd1eq9fuknhe60XCri3k7FmHcKax0NQ3AfG23VwhtgMIIDPzCCAqigAwIB
AgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UE
CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUu
Y29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7
TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRA
HmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYy
aHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0P
BAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG
9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8
/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQ
Gls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYwYjELMAkGA1UEBhMCWkExJTAj
BgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz
b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBNk3riVqa6V5DKodSEpLMAMAkGBSsOAwIaBQCgggFv
MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MDcxNzIwMTkzMlow
IwYJKoZIhvcNAQkEMRYEFHcwmuqKVxeOOkQiNiz2WIf4bgraMIGFBgkrBgEEAYI3EAQxeDB2MGIx
CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD
VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQTZN64lamuleQyqHUhKSz
ADCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIQTZN64lamuleQyqHUhKSzADANBgkqhkiG9w0BAQEFAASCAQAzHgyMU8gXZbNdeikm
bkp/F3dvE5+Qgwvl65h9AEH3Lm58G43AcxwCZ1kM73/g9DFEXFtPSZlZua5Rbsb1a5MSJU/ncTMI
DCI9MQH0nz1a0wgP3fN54NzpeEf78YbyiIB3nBTU+di+PfPzoa9CW5GBVwxrC4RZSOC5dpI5Xlcz
E0Ne4eo7nL0B+1eifxorNil2jStAyuNt6VgROJFPHK2/QCr/Cc0T1Wq+3u0BXmRkT++H8CXpLmE7
dOoRYJoRsZOWtQiR182gLD4dW068Kwki+41+A4Fq3GQ6Ut462tspnmZuxw8QsXfBHdhVD7eY6NDp
qimjcH+VWcdpsNIKLth9AAAAAAAA
--Apple-Mail-385--351913207--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]