From 99e0800d1e1af4c3fd7e221cdcd4d954a863e68e Mon Sep 17 00:00:00 2001 From: Ari Chivukula Date: Fri, 15 Mar 2024 11:44:56 +0000 Subject: [PATCH] fix --- .github/workflows/pages.yml | 2 +- .python-version | 1 + Makefile | 3 +- spec.html | 495 ++++++++++++++++++++++++++++++++++++ 4 files changed, 498 insertions(+), 3 deletions(-) create mode 100644 .python-version create mode 100644 spec.html diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index 5e64289..43724c4 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -21,9 +21,9 @@ jobs: - uses: actions/checkout@v4 - uses: actions/setup-python@v5 with: - python-version: '3.12' cache: 'pip' - run: pip install -r requirements.txt + - run: bikeshed update - run: make - uses: actions/upload-pages-artifact@v3 with: diff --git a/.python-version b/.python-version new file mode 100644 index 0000000..e4fba21 --- /dev/null +++ b/.python-version @@ -0,0 +1 @@ +3.12 diff --git a/Makefile b/Makefile index 44ce135..5a2c388 100644 --- a/Makefile +++ b/Makefile @@ -10,5 +10,4 @@ clean: build/index.html: spec.bs Makefile mkdir -p build - bikeshed update - bikeshed --die-on=warning spec + bikeshed --die-on=warning spec $< $@ diff --git a/spec.html b/spec.html new file mode 100644 index 0000000..bc61bf7 --- /dev/null +++ b/spec.html @@ -0,0 +1,495 @@ + + + + Extending Storage Access API (SAA) to non-cookie storage + + + + + + + + + + + + + + +
+

+

Extending Storage Access API (SAA) to non-cookie storage

+

Draft Community Group Report,

+
+
+
This version: +
https://privacycg.github.io/saa-non-cookie-storage/ +
Issue Tracking: +
GitHub +
Editors: +
(Google) +
(Google) +
+
+
+

Copyright © 2024 the Contributors to “Extending Storage Access API (SAA) to non-cookie storage”, published by the Privacy Community Group. + +This document is licensed under the Creative Commons Attribution 4.0 International License. + +Contributions to this document are made under the W3C Community Contributor License Agreement (CLA).

+
+
+
+

Abstract

+

This extends the Storage Access API to enable content in cross-site iframes to request access to first-party data beyond cookies.

+
+

Status of this document

+
+

This specification is intended to be merged into the HTML Living Standard. It is neither a WHATWG Living Standard nor is it on the standards track at W3C.

+

It was published by the Privacy Community Group. +Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. +Learn more about W3C Community and Business Groups.

+
+
+ +
+
+

Conformance

+

Document conventions

+

Conformance requirements are expressed + with a combination of descriptive assertions + and RFC 2119 terminology. + The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” + in the normative parts of this document + are to be interpreted as described in RFC 2119. + However, for readability, + these words do not appear in all uppercase letters in this specification.

+

All of the text of this specification is normative + except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

+

Examples in this specification are introduced with the words “for example” + or are set apart from the normative text + with class="example", + like this:

+
+ +

This is an example of an informative example.

+
+

Informative notes begin with the word “Note” + and are set apart from the normative text + with class="note", + like this:

+

Note, this is an informative note.

+
+ +

References

+

Normative References

+
+
[RFC2119] +
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119 +
\ No newline at end of file