mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-17 03:24:37 -05:00
update xdi info
This commit is contained in:
parent
f2e4a9e09c
commit
01a6fbbd85
@ -9,12 +9,12 @@ excerpt: >
|
||||
XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node.
|
||||
description: "XDI is a graph-based data model. This means that all data is expressed using nodes and arcs in a graph. At a minimum, a graph consists of a single node, called the common root node."
|
||||
layout: single
|
||||
permalink: web-standards/oasis-open/xdi/xdi/
|
||||
permalink: web-standards/oasis-open/xdi/xri-data-interchange/
|
||||
canonical_url: 'https://decentralized-id.com/web-standards/oasis-open/xdi/xdi/'
|
||||
redirect_from:
|
||||
- web-standards/oasis-open/xdi/xdi/
|
||||
- web-standards/xdi/
|
||||
- specs-standards/xdi/
|
||||
- standards/xdi
|
||||
- standards/xdi/
|
||||
categories: ["Web Standards"]
|
||||
tags: ["XDI","Danube Tech","OASIS","BTCR","W3C","Planetwork","Indy"]
|
||||
@ -46,7 +46,6 @@ The XNS Public Trust Organization was founded in July 2000, shortly after Intern
|
||||
>
|
||||
> This white paper presents several examples of classic cross-domain data sharing problems, explains how the Dataweb model can provide a generalized solution, and describes the key objectives of the newlyformed OASIS XDI Technical Committee ([http://www.oasis-open.org/committees/xdi](http://www.oasis-open.org/committees/xdi)).
|
||||
|
||||
|
||||
## RWoT Papers
|
||||
|
||||
* [Cool hack with XDI graphs, blockstore, link contracts, and cryptographic identifiers](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/cool-hack-xdi-blockstore-bip32.md)
|
||||
|
@ -68,4 +68,13 @@ header:
|
||||
> | Trusted resolution options | DNSSEC | HTTPS and/or SAML |
|
||||
> | Resolution client | resolver | resolver |
|
||||
> | Resolution server | authoritative nameserver | authority server |
|
||||
> | Recursing resolution | recursing nameserver | recursing authority server or proxy resolver |
|
||||
> | Recursing resolution | recursing nameserver | recursing authority server or proxy resolver |
|
||||
|
||||
## i-names
|
||||
|
||||
* [inames](https://web.archive.org/web/20150801134550/http://inames.net/)
|
||||
> URLs are for connecting web pages. Now get the address for connecting people and businesses in rich, long-lasting digital relationships: i-names.
|
||||
* [http://dev.inames.net/wiki/Main_Page](https://web.archive.org/web/20111001110114/http://dev.inames.net/wiki/Main_Page)
|
||||
> The goal of this wiki is to be a portal for everything XRI and i-names developers need to know to integrate i-names and XRI infrastructure into their identity-enabled sites, services, and applications. Please let us know via the About Us page if you don't find what you are looking for, or just add a request directly to the wiki.
|
||||
* [I Names](https://en.wikipedia.org/wiki/I-name)
|
||||
> I-names are one form of an XRI — an OASIS open standard for digital identifiers designed for sharing resources and data across domains and applications.[1] I-names are human readable XRIs intended to be as easy as possible for people to remember and use. For example, a personal i-name could be =Mary or =Mary.Jones. An organizational i-name could be @Acme or @Acme.Corporation.
|
||||
|
Loading…
Reference in New Issue
Block a user