Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Strawman Object model for XDI for the discussion at XDI f2f meeting New Orleans 2004-04-29 Nat Sakimura.

Similar presentations


Presentation on theme: "1 Strawman Object model for XDI for the discussion at XDI f2f meeting New Orleans 2004-04-29 Nat Sakimura."— Presentation transcript:

1 1 Strawman Object model for XDI for the discussion at XDI f2f meeting New Orleans Nat Sakimura

2 © 2004 NRI 2 XDI Intro Whitepaper model is hard to read … and, some of the requirements are not met.

3 © 2004 NRI 3 Proposed Straw man XDI Object Model (extremely rough and incomplete sketch for discussion) Changes: Inheritance used. Resources has more for efficiency Contract is a subclass of Resource, thereby introducing further structure Some elementally methods shown.

4 © 2004 NRI 4 links in Resource may be a bad naming as it can be confused with links in the whitepaper. It simply is a link to the external document. Link in the witepaper is more akin to Contract here.

5 © 2004 NRI 5 Some Considerations on Resources type – dictates what object type this XDI document is ename – for efficiency enumbers – must have at least one of this. links – links to external XDI documents ref – links to the enveloping XDI document resources – Resource can contain other resources. effectiveDate – do we need it? expiryDate – ditto cacheable – ditto cachePeriod – ditto

6 © 2004 NRI 6 Some considerations on Contracts (link in the whitepaper) parties – contracts are among two or more parties. jurisdiction – any contract needs jurisdiction Other standard feature of contracts needs to be added as well? Or – should we construct each part as sub-resources? (see next slide) templateID – a resource with human readable data in which parties are written as variables can be used as template. This, combined with parities above, can derive a human readable contract. (Note: xri itself will be the machine readable version of the contract template. ) date – maybe needed only as the part of dsigs? dsigs – XML digital signature

7 © 2004 NRI 7 Should we stick with the generics? Generics as in the Whitepaper :1:3:58 =John_Smith =Johnny (+type) :1:3:58:3 (+person) …. Expanded (+person) :1:3:58 =John_Smith =Johnny … Sticking with the generics may be esthetically appealing, but may be inefficient in the implementation. We don ’ t have to register the fact that :1:3:58 is type +person as addressable resource. It has no use, and the registration is very expensive computationally. More over, it is much easier to constrain that the particular resource has only one type if we had.


Download ppt "1 Strawman Object model for XDI for the discussion at XDI f2f meeting New Orleans 2004-04-29 Nat Sakimura."

Similar presentations


Ads by Google