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

New datapackage.json field: author (or creator) #130

Closed
rufuspollock opened this Issue Jun 10, 2014 · 8 comments

Comments

Projects
None yet
3 participants
@rufuspollock
Contributor

rufuspollock commented Jun 10, 2014

npm introduces author field (not in commonjs spec i believe which just has contributors and maintainers).

Relatedly: should field be called author or creator? I prefer author but creator aligns with dublincore ...

npm

### people fields: author, contributors

The "author" is one person. "contributors" is an array of people. A "person" is an object with a "name" field and optionally "url" and "email", like this:

{ "name" : "Barney Rubble"
, "email" : "b@rubble.com"
, "url" : "http://barnyrubble.tumblr.com/"
}
Or you can shorten that all into a single string, and npm will parse it for you:

"Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)
Both email and url are optional either way.

npm also sets a top-level "maintainers" field with your npm user info.
@rufuspollock

This comment has been minimized.

Contributor

rufuspollock commented Aug 2, 2014

More generally: should we slim down what we "RECOMMEND" in terms of key fields. Options:

  • author
  • creator (following dublin core)
  • contributors
  • maintainers
  • publishers

I would argue for one of of author/creator (prefer author) and dropping maintainers for contributors.

@rufuspollock

This comment has been minimized.

Contributor

rufuspollock commented Aug 17, 2014

Have to say I strongly prefer author to creator based on semantics (creator is pretty ambiguous IMHO). I'm not sure about merging maintainers and contributers though.

@rufuspollock

This comment has been minimized.

Contributor

rufuspollock commented Apr 21, 2015

@paulfitz @jpmckinney @pwalsh any thoughts on:

  • introducing author (and using author rather than creator)
  • merging maintainers and contributors (what's the difference? i get confused myself!)
@pwalsh

This comment has been minimized.

Member

pwalsh commented Apr 21, 2015

+1 on maintainers and contributors -> contributors - a clear win.
+1 on creator -> author for on semantic reasons, but wouldn't feel too strongly about it if it didn't change.

@jpmckinney

This comment has been minimized.

Member

jpmckinney commented Apr 21, 2015

Matching Dublin Core's term creator would be nice, but author is a fine substitute. Schema.org offers both author and creator, as I guess they had the same reaction to the intuitiveness of creator; I prefer offering a single term. Dublin Core has contributor, so I prefer it to maintainer.

@rufuspollock

This comment has been minimized.

Contributor

rufuspollock commented May 6, 2015

OK, so i think we have a decision:

  • author
  • contributors field and no maintainer.

I will make the change.

@rufuspollock

This comment has been minimized.

Contributor

rufuspollock commented May 26, 2015

I note I also propose we remove publishers in favour of contributors.

@pwalsh

This comment has been minimized.

Member

pwalsh commented May 26, 2015

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