Difference between revisions of "Purpose"

From MgmtWiki
Jump to: navigation, search
(Problems)
(Definition)
Line 1: Line 1:
 
==Definition==
 
==Definition==
 
In essence, function serves as the means to achieve a purpose, enabling the fulfillment of a desired outcome. While function emphasizes practicality and utility, purpose delves into the underlying motivation or meaning behind an object or action.
 
In essence, function serves as the means to achieve a purpose, enabling the fulfillment of a desired outcome. While function emphasizes practicality and utility, purpose delves into the underlying motivation or meaning behind an object or action.
 +
 +
==Flow==
 +
For the purpose satisfied by some sort of digital presentment:
 +
# Desired outcome = typically access to some resource
 +
# Purpose = Enabling the desired outcome
 +
# Function = the algorithm or steps to follow to achieve the purpose
 +
# Query = the message that asks for specific action to enable the access
 +
# Wallet = the code that receives the query an asks the holder for consent (it must convert the query into a display)
 +
# Consent = the holder action that allows a response
 +
# Grant = the message that is returned in response to the query (it may be sufficient)
 +
# Verify = the code that accepts the grant and determines if the grant is sufficient
 +
# Response = either a rejection, a new query or admission to the requested resource
 +
Note that cycles are possible to achieve the desired outcome.
  
 
==Problems==
 
==Problems==

Revision as of 17:16, 12 April 2024

Definition

In essence, function serves as the means to achieve a purpose, enabling the fulfillment of a desired outcome. While function emphasizes practicality and utility, purpose delves into the underlying motivation or meaning behind an object or action.

Flow

For the purpose satisfied by some sort of digital presentment:

  1. Desired outcome = typically access to some resource
  2. Purpose = Enabling the desired outcome
  3. Function = the algorithm or steps to follow to achieve the purpose
  4. Query = the message that asks for specific action to enable the access
  5. Wallet = the code that receives the query an asks the holder for consent (it must convert the query into a display)
  6. Consent = the holder action that allows a response
  7. Grant = the message that is returned in response to the query (it may be sufficient)
  8. Verify = the code that accepts the grant and determines if the grant is sufficient
  9. Response = either a rejection, a new query or admission to the requested resource

Note that cycles are possible to achieve the desired outcome.

Problems

  • The number of purposes is indefinite. Which means that it is not possible to enumerate all purposes.
  • In fact the very existence of Digital Identifiers will create an environment which possible purpose that have never been expected.

References