[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 TC Telecon Thursday 1-2PM PT 2008-07-10)
Hi Marcus,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.
> 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.
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<http://open.org/apps/org/workgroup/xdi/document.php?document_id=28380><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/xdi/XdiOneIssues/LinkContractPattern>
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/apps/org/workgroup/portal/my_workgroups.php>
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
---------------------------------------------------------------------
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]