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

Add a property on CreativeWork to specify access rights #2173

Open
anarchivist opened this issue Mar 12, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@anarchivist
Copy link

commented Mar 12, 2019

It would be useful to specify access rights for CreativeWorks. This was originally surfaced as part of the proposal made for Schema Architypes, an extension for archives and their collections, but in discussion, it became clear that this applies to lots of other domains, including other materials held by cultural heritage institutions, datasets created and used in research, and so forth.

I believe access rights should be understood as distinct from license and hasDigitalDocumentPermission.

Examples:

An archival collection:

{
  "@context": "http://schema.org/",
  "@type": "Collection",
  "url": "https://www.lib.ncsu.edu/findingaids/mc00351",
  "name": "Animal Rights Network records",
  "accessRights": "This collection is open for research; access requires at least 48 hours advance notice."
}

A digitized letter from an archival collection:

{
  "@context": "http://schema.org/",
  "@type": "CreativeWork",
  "url": "https://purl.stanford.edu/bp158wj7223",
  "name": "Margaret Mitchell letter to Herschel Bricknell, 1936 August 22",
  "accessRights": "Online content is available for access via the Special Collections Reading Room."
}

A dataset:

{
  "@context": "http://schema.org/",
  "@type": "Dataset",
  "@id": "https://doi.org/10.7910/DVN/0OLJLM",
  "name": "Restricted Access WFHS Leef Manager Linking Data, Version 1.0",
  "accessRights": "Access to this dataset can be obtained by visiting the Work, Family & Health Network web page and following the instructions: http://projects.iq.harvard.edu/wfhn/restricted-access-data."
}

Additional context and examples:

See past discussion on #1784, #1758, #1759, and #900 (comment).

@RichardWallis

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2019

The more I look at this possibility/proposal the more sense it makes to me.

OK, its probably not applicable to all CreativeWork subtypes (e.g. menu, howTo, Question) but I can think of scenarios where it would be applicable to a large proportion of the rest.

@anarchivist anarchivist changed the title Add an property on CreativeWork to specify access rights Add a property on CreativeWork to specify access rights Mar 13, 2019

RichardWallis pushed a commit that referenced this issue Apr 10, 2019

@danbri

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2019

accessRights is the wrong name for this. Lets call it accessInfo.

"access requires at least 48 hours advance notice" isn't really about rights to anything for anyone, if anything it is closer to openingHours. Same for ""Access to this dataset can be obtained by visiting the Work, Family & Health Network web page and following the instructions: http://projects.iq.harvard.edu/wfhn/restricted-access-data.", "Online content is available for access via the Special Collections Reading Room."

@RichardWallis

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2019

Suggested alternative property name 'conditionsOfAccess'

With description:
Conditions that affect the availability of, or method(s) of access to, the item. For example "Available by appointment from the Reading Room" or "Accessible only from logged-in accounts ".

cc/ @anarchivist

danbri added a commit that referenced this issue Jun 18, 2019

Add new property 'accessRights' with domainIncludes 'CreativeWork' (#…
…2205)

* Added new property 'accessRights' with domainIncludes 'CreativeWork' - issue: #2173

* Change property name to conditionsOfAccess

@ashepherd ashepherd referenced this issue Jun 18, 2019

Open

Review Schema.org release 3.8 #20

0 of 2 tasks complete
@anarchivist

This comment has been minimized.

Copy link
Author

commented Jun 18, 2019

Either of the two proposed alternate property names sound fine to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.