Difference between revisions of "R-Card"

Latest revision as of 20:40, 18 July 2011

See http://www.eclipse.org/higgins/documents/relationship-cards.html

@@ Line 1: / Line 1: @@
-== About ==
+{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
-This page provides the Higgins definition of an '''r-card''' ("relationship card").
+[[Image:Higgins_logo_76Wx100H.jpg|right]]
+See http://www.eclipse.org/higgins/documents/relationship-cards.html
-== R-Card Functionality ==
-An r-card is a superset of the functionality of an m-card as defined by the MS ISIP specification. The differences are:
-* Both r-cards and m-cards include a pointer to the issuer's STS for obtaining a security token.
-* An r-card includes a second pointer: a Higgins [[Relation]] to the [[Digital Subject]] to which the r-card applies. This relation is provisioned by the r-card issuer, and points to the [[Digital Subject]] in the [[Context]] designated by the issuer.
-* An r-card capable [[Selector]] receiving this r-card can resolve the [[ContextId]] of the [[Relation]] (see that page for details) to discover the data sharing protocol by which the selector can communicate with the designated context. Any protocol can be used; [[XDI]] is one protocol designed for this purpose.
-== R-Card Extension to the M-Card Schema ==
-The only extension necessary is a single element, '''Relation''', from the Higgins namespace. Following are examples of such an element:
-RelationURI:
-<pre>
-<higgins:Relation>http://ldap.example.com/ldap.xrds#username</higgins:Relation>
-</pre>
-RelationXRI (using XRI 2.0 syntax):
-<pre>
-<higgins:Relation>xri://=example.name/($context)*($ldap)//username</higgins:Relation>
-</pre>

Breadcrumbs

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Difference between revisions of "R-Card"

Latest revision as of 20:40, 18 July 2011