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

Specify data shape for article notifications #8

Open
csarven opened this issue Aug 31, 2017 · 1 comment
Open

Specify data shape for article notifications #8

csarven opened this issue Aug 31, 2017 · 1 comment

Comments

@csarven
Copy link
Member

csarven commented Aug 31, 2017

Article in the generic sense of the word. It could include manuscripts, scholarly articles, notes, slides, reviews, thesis etc. There may be some overlap with issue #9 but that's fine.

@csarven
Copy link
Member Author

csarven commented Sep 5, 2017

MUST include:

# No need to declare the URI of the notification.
<>
  a as:Announce ;
# A valid xsd:dateTime.
  as:updated "2017-09-05T21:11:58.611Z"^^xsd:dateTime ;
# CC0 license must be declared here.
  schema:license <https://creativecommons.org/publicdomain/zero/1.0/> ;
# URI of the article that's being announced
  as:object <http://csarven.ca/dokieli-rww> .

# A class along the lines of schema:ScholarlyArticle, sioc:Post,
# foaf:Document, sioc:Post, biblio:Paper, bibo:Document, as:Article.
<http://csarven.ca/dokieli-rww>
  a schema:ScholarlyArticle .

SHOULD include:

# URI of the agent (but not the software) that sent the notification.
<>
  as:actor <http://csarven.ca/#i> .

# URI of an open/free culture license on the article is expected here.
<http://csarven.ca/dokieli-rww>
  schema:license <https://creativecommons.org/licenses/by/4.0/> .

MAY include:
Anything else that may help with the reuse of this notification or discovery of the resources it refers to. This doesn't mean that the body of the referred resources should be copied here.

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