search

samvera-deprecated / rdf-vocab

Shared RDF Vocabularies (rdf-vocab <= v0.7.0)
https://github.com/ruby-rdf/rdf-vocab
Apache License 2.0
4 stars 2 forks source link

added MODS rdf vocab #2

Closed acoburn closed 10 years ago

acoburn commented 10 years ago

This adds a modsrdf vocabulary, following the documentation here http://www.loc.gov/standards/mods/modsrdf/v1/ (plus the elements dateIssued, dateIssuedStart and dateIssuedEnd), which are strangely absent from the draft document.

mjgiarlo commented 10 years ago

Hi @acoburn! Thanks for the submission. I scanned the list of Hydra licensed contributors, and I didn't find your name on the list. Before we merge this, can you sign a Contributor License Agreement?

All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Hydra Project Steering Group, a process which is initiated by completing an iCLA and emailing it to legal@projecthydra.org. If the contributor works for an institution which has rights over materials that they contribute, the institution should also have a Corporate Contributor License Agreement (cCLA) on file; when no such cCLA exists the potential contributor will be asked to confirm in an email to legal@projecthydra.org, copied to their line manager, that they have institutional authorization to enter into the iCLA.

More here: https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership

acoburn commented 10 years ago

Hello, Attached is a signed CLA.

Aaron Coburn

On Jun 5, 2014, at 9:30 PM, Michael J. Giarlo notifications@github.com wrote:

Hi @acoburn! Thanks for the submission. I scanned the list of Hydra licensed contributors, and I didn't find your name on the list. Before we merge this, can you sign a Contributor License Agreement?

All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Hydra Project Steering Group, a process which is initiated by completing an iCLA and emailing it to legal@projecthydra.org. If the contributor works for an institution which has rights over materials that they contribute, the institution should also have a Corporate Contributor License Agreement (cCLA) on file; when no such cCLA exists the potential contributor will be asked to confirm in an email to legal@projecthydra.org, copied to their line manager, that they have institutional authorization to enter into the iCLA.

More here: https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership

— Reply to this email directly or view it on GitHub.

mjgiarlo commented 10 years ago

@acoburn You'll want to send that to legal@projecthydra.org, and that should kick things off. When you're added to the list o' contributors on the wiki, we can get these moving. (Sorry for the delay!)

acoburn commented 10 years ago

@mjgiarlo yes, I cc'ed it to legal@projecthydra.org in the first message, but let me know if there's anything else needed.

mjgiarlo commented 10 years ago

Ah, great. GitHub did not alert me to that. Nope, you've done all that you need at this point. Should it be determined that you need a corporate CLA on file as well, that'll be another step, but here's hoping you're done!

mjgiarlo commented 10 years ago

@acoburn is now on the list of contributors: https://wiki.duraspace.org/x/vs4QAg. Merging.