Difference between revisions of "Federation Trust Registry"

From MgmtWiki
Jump to: navigation, search
(External Sources)
m (External Sources)
Line 17: Line 17:
  
 
===External Sources===
 
===External Sources===
OAuth 2.0 Dynamic Client Registration Protocol RFC 7591
+
*OAuth 2.0 Dynamic Client Registration Protocol RFC 7591
[https://www.ietf.org/mail-archive/web/oauth/current/msg18101.html Email thread that suggests use of software statements to provide federation].
+
*[https://www.ietf.org/mail-archive/web/oauth/current/msg18101.html Email thread that suggests use of software statements to provide federation].

Revision as of 15:41, 14 September 2018

Full Title or Meme

Wherever a Web Sites wishes to take advantage of the benefits of belonging to a Federation it needs to be exposed in a Data Service that allows any user to ensure that the Web Site has been Validated by the Federation.

Solution

In order that a Federation can be expose both is principles and its membership to the public some data server needs to provide information about the existing membership and their status. There are two ways to do this:

  1. A list of the members and their status that can be viewed in a browser.
  2. A data service that exposes the contents of the site in machine readable format.

This page is about the later case.

Of primary importance for a Federation that wants to allow user's to trust the members, is some easily accessible data service on a site that meets the following criteria[1]

  1. Reliable, always-on accessibility.
  2. Meta-data descriptions of the contents of the site.
  3. Machine readable data as well as meta-data (called Service-Enabled Data Store).
  4. Data Security

References

  1. Michael J. Carey +2, Data Services (2012-06) CACM 55 No 6 Pp. 86-97

External Sources