Skip to content
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.

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

Access Control Document #48

Open
michaelsena opened this issue Jul 1, 2020 · 1 comment
Open

Access Control Document #48

michaelsena opened this issue Jul 1, 2020 · 1 comment

Comments

@michaelsena
Copy link
Member

michaelsena commented Jul 1, 2020

cip: 
title: Access Control Document
author: Michael Sena (@michaelsena), Joel Thorstensson (@oed)
discussions-to:
status: Idea
category: Standards
type: RFC
created: 2020-07-01
requires: Tile Doctype (CIP-8)
replaces: 

🚨 This is a placeholder for an idea, and we will work to draft the CIP at a later time.

Simple Summary

The Access Control Document provides an access control module that can be used to add privacy features to any Ceramic document.

Abstract

Abstract goes here.

Motivation

Motivation goes here.

Specification

Specification goes here.

Rationale

Rationale goes here.

Backwards Compatibility

Backwards compatibility goes here.

Implementation

Implementation goes here.

Security Considerations

Security considerations go here.

Copyright

Copyright and related rights waived via CC0.

@michaelsena
Copy link
Member Author

@oed I think we should make accessControl an optional meta property (alongside owners, schema, tags, etc) of a document included in the general Doctype specification (both genesis and signed). This would allow users to plug in a reference to some access control provider (either Ceramic document as described in this issue), or some other mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant