Skip to content

Integrate access request terminology with main terminology section #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
acoburn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Integrate access request terminology with main terminology section #218

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions lws10-core/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,17 @@ <h2>Terminology</h2>
This specification defines the following terms:
</p>
<ul>
<li><dfn>access grant</dfn> &mdash; a data object created by a <a>storage controller</a>, expressing
an ability for an <a>agent</a> to perform specific actions on <a>storage</a> resources within certain
defined constraints.</li>
<li><dfn data-lt="access profiles">access profile</dfn> &mdash; an access profile describes the
requirements for expressing a valid access policy. Every access profile is identified
with a URI, and a server indicates support for one or more access profiles by
referencing them in the <code>conformsTo</code> property of a service object in its
<a>storage description</a> resource.</li>
<li><dfn>access request</dfn> &mdash; a data object submitted by an <a>agent</a>, expressing a
request to perform specific actions on storage resources, including the desired scope
and constraints.</li>
<li><dfn data-lt="agents">agent</dfn> &mdash; a person, social entity, or software identified by a URI.</li>
<li><dfn data-lt="authentication credentials">authentication credential</dfn> &mdash; a security token that asserts claims about an <a>agent</a> or end-user. This token is secured with a cryptographic proof.
Examples of authentication credentials include assertions of identity such as OpenID Connect ID Tokens and SAML-based assertions as well as assertions of
Expand Down
26 changes: 0 additions & 26 deletions lws10-core/lws-access-requests.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,32 +19,6 @@
actions, constraints, and assignees. Other profiles could use a different conceptual framework.
</p>

<div class="issue" title="Integrate with main terminology section">
<p>
This section defines the following terms:
</p>

<ul>
<li>
<dfn>Access Request</dfn> &mdash; a data object submitted by an <a>agent</a>, expressing a
request to perform specific actions on storage resources, including the desired scope
and constraints.
</li>
<li>
<dfn>Access Grant</dfn> &mdash; a data object created by a <a>storage controller</a>, expressing
an ability for an <a>agent</a> to perform specific actions on <a>storage</a> resources within certain
defined constraints.
</li>
<li>
<dfn data-lt="access profiles">Access Profile</dfn> &mdash; an access profile describes the
requirements for expressing a valid access policy. Every access profile is identified
with a URI, and a server indicates support for one or more access profiles by
referencing them in the <code>conformsTo</code> property of a service object in its
<a>storage description</a> resource.
</li>
</ul>
</div>

<section id="access-discovery">
<h3>Discovery</h3>

Expand Down