Difference between revisions of "Resource"

From MgmtWiki
Jump to: navigation, search
(Problems)
(Full Title or Meme)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Full Title or Meme==
 
==Full Title or Meme==
  
A part of a [[Web Site]] that provides access to service or content on the internet.  
+
For the purposes of this wiki, a [[Resource]] is:
 +
# access to some physical or digital capability or venue that is restricted to eligible users,
 +
# that part of a [[Web Site]] that provides access to service or content on the internet.
  
 
==Context==
 
==Context==
 +
*While resource can be real-world [[Entity|Entities]], in this wiki it will be assumed by default that they are digiial.
 
*Resources are something typically need to be protecting with [[Authentication]] by a [[Identifier or Attribute Provider]] - either identity data of your users, or APIs.
 
*Resources are something typically need to be protecting with [[Authentication]] by a [[Identifier or Attribute Provider]] - either identity data of your users, or APIs.
 
*Every resource has a unique name - and clients use this name to specify to which resources they want to get access to.
 
*Every resource has a unique name - and clients use this name to specify to which resources they want to get access to.
Line 13: Line 16:
  
 
==Solutions==
 
==Solutions==
 +
*Resources may have names or [[Identifier]]s, on the internet that would be the [[URI]].
 +
*Resources will have locations, on the internet that would be a [[URL]].
  
 
==References==
 
==References==

Latest revision as of 09:53, 1 November 2023

Full Title or Meme

For the purposes of this wiki, a Resource is:

  1. access to some physical or digital capability or venue that is restricted to eligible users,
  2. that part of a Web Site that provides access to service or content on the internet.

Context

  • While resource can be real-world Entities, in this wiki it will be assumed by default that they are digiial.
  • Resources are something typically need to be protecting with Authentication by a Identifier or Attribute Provider - either identity data of your users, or APIs.
  • Every resource has a unique name - and clients use this name to specify to which resources they want to get access to.
  • The Resource will typically use User Information (aka claims) about a user (name, email address, etc.) to enable Persistence, Recovery and Redress for the user.
  • API resources represent functionality a client wants to invoke - typically modelled as Web APIs, but not necessarily.

Problems

Solutions

  • Resources may have names or Identifiers, on the internet that would be the URI.
  • Resources will have locations, on the internet that would be a URL.

References