Difference between revisions of "Privacy Policy"
From MgmtWiki
(Created page with "==Full Title or Meme== A naans for creating a policy that applies to a transaction. ==Context== ==Existing Work== * [https://www.youtube.com/watch?v=ubqKJAizayU&authuser=0 C...") |
(→Existing Work) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
| − | A | + | A means for creating a policy that applies to a transaction or a registration. |
==Context== | ==Context== | ||
==Existing Work== | ==Existing Work== | ||
| − | * [https:// | + | * Also see wiki [[AuthZen]] |
| + | * 2025 [https://openid.github.io/authzen/ AuthZEN - Authorization API]<blockquote>The Authorization API enables Policy Decision Points (PDPs) and Policy Enforcement Points (PEPs) to communicate authorization requests and decisions to each other without requiring knowledge of each other's inner workings. The Authorization API is served by the PDP and is called by the PEP. The Authorization API includes an Evaluation endpoint, which provides specific access decisions. Other endpoints may be added in the future for other scenarios, including searching for subjects, resources or actions.</blockquote> | ||
| + | * [https://datatracker.ietf.org/doc/html/rfc47450 Common Policy: A Document Format for Expressing Privacy Preferences draft-ietf-geopriv-common-policy-11.txt] RFC 4745 (2007-02) <blockquote> This document defines a framework for authorization policies controlling access to application specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains. </blockquote> | ||
| + | * [https://www.linkedin.com/pulse/combining-ace-owl-odrl-new-paradigm-privacy-georg-philip-krog-9xmvf/?trackingId=lduWtJZJAgDSmmpg3UGnWQ%3D%3D Combining ACE, OWL, and ODRL: A New Paradigm for Privacy Documentation] 2025-02-10 <blockquote>As privacy regulations evolve globally, we need better tools to express, manage, and verify privacy policies. Here's how combining Attempto Controlled English (ACE), Web Ontology Language (OWL), and Open Digital Rights Language (ODRL) creates a powerful framework for privacy documentation.</blockquote> | ||
==References== | ==References== | ||
[[Category: Privacy]] | [[Category: Privacy]] | ||
| + | [[Category: Policy]] | ||
Latest revision as of 11:55, 28 August 2025
Full Title or Meme
A means for creating a policy that applies to a transaction or a registration.
Context
Existing Work
- Also see wiki AuthZen
- 2025 AuthZEN - Authorization API
The Authorization API enables Policy Decision Points (PDPs) and Policy Enforcement Points (PEPs) to communicate authorization requests and decisions to each other without requiring knowledge of each other's inner workings. The Authorization API is served by the PDP and is called by the PEP. The Authorization API includes an Evaluation endpoint, which provides specific access decisions. Other endpoints may be added in the future for other scenarios, including searching for subjects, resources or actions.
- Common Policy: A Document Format for Expressing Privacy Preferences draft-ietf-geopriv-common-policy-11.txt RFC 4745 (2007-02)
This document defines a framework for authorization policies controlling access to application specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.
- Combining ACE, OWL, and ODRL: A New Paradigm for Privacy Documentation 2025-02-10
As privacy regulations evolve globally, we need better tools to express, manage, and verify privacy policies. Here's how combining Attempto Controlled English (ACE), Web Ontology Language (OWL), and Open Digital Rights Language (ODRL) creates a powerful framework for privacy documentation.
