ldp 0.7.1 → 1.0.3

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+The Samvera community is dedicated to providing a welcoming and
+positive experience for all its members, whether they are at a formal
+gathering, in a social setting, or taking part in activities online.
+The Samvera community welcomes participation from people all over the
+world and these members bring with them a wide variety of
+professional, personal and social backgrounds; whatever these may be,
+we treat colleagues with dignity and respect.
+
+Community members communicate primarily in English, though for many of
+them this is not their native language. We therefore strive to express
+ourselves simply and clearly remembering that unnecessary use of
+jargon and slang will be a barrier to understanding for many of our
+colleagues.  We are sensitive to the fact that the international
+nature of the community means that we span many different social norms
+around language and behaviour and we strive to conduct ourselves,
+online and in person, in ways that are unlikely to cause offence.
+
+Samvera conversations are often information-rich and intended to
+generate discussion and debate.  We discuss ideas from a standpoint of
+mutual respect and reasoned argument.
+
+Community members work together to promote a respectful and safe
+community. In the event that someone’s conduct is causing offence or
+distress, Samvera has a detailed
+[Anti-Harassment Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+which can be applied to address the problem. The first step in dealing
+with any serious misconduct is to contact a local meeting organizer,
+the
+[Samvera community helpers](https://wiki.duraspace.org/display/samvera/Samvera+Community+Helpers)
+([email](mailto:helpers@samvera.org)), a community member you
+trust, or the
+[Samvera Steering Group](https://wiki.duraspace.org/display/samvera/Samvera+Steering+Group+membership)
+immediately; at Samvera events, these people can be identified by
+distinctive name badges. The
+[Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+should be consulted for fuller details.

data/CONTRIBUTING.md

@@ -1,24 +1,49 @@
 # How to Contribute
 
-We want your help to make Project Hydra great.
-There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
+We want your help to make the Samvera community great. There are a few guidelines
+that we need contributors to follow so that we can have a chance of
+keeping on top of things.
 
 ## Code of Conduct
 
-The Hydra community is dedicated to providing a welcoming and positive experience for all its
-members, whether they are at a formal gathering, in a social setting, or taking part in activities
-online.  Please see our [Code of Conduct](https://wiki.duraspace.org/display/hydra/Code+of+Conduct)
-for more information.
+The Samvera Community is dedicated to providing a welcoming and positive
+experience for all its members, whether they are at a formal gathering, in
+a social setting, or taking part in activities online. Please see our
+[Code of Conduct](CODE_OF_CONDUCT.md) for more information.
 
-## Hydra Project Intellectual Property Licensing and Ownership
+## Samvera Community Intellectual Property Licensing and Ownership
 
-All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Hydra Project Steering Group.
-If the contributor works for an institution, the institution must have a Corporate Contributor License Agreement (cCLA) on file.
+All code contributors must have an Individual Contributor License Agreement
+(iCLA) on file with the Samvera Steering Group. If the contributor works for
+an institution, the institution must have a Corporate Contributor License
+Agreement (cCLA) on file.
 
-https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership
+https://wiki.duraspace.org/display/samvera/Samvera+Community+Intellectual+Property+Licensing+and+Ownership
 
 You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.
 
+## Language
+
+The language we use matters.  Today, tomorrow, and for years to come
+people will read the code we write.  They will judge us for our
+design, logic, and the words we use to describe the system.
+
+Our words should be accessible.  Favor descriptive words that give
+meaning while avoiding reinforcing systemic inequities.  For example,
+in the Samvera community, we should favor using allowed\_list instead
+of whitelist, denied\_list instead of blacklist, or source/copy
+instead of master/slave.
+
+We're going to get it wrong, but this is a call to keep working to
+make it right.  View our code and the words we choose as a chance to
+have a conversation. A chance to grow an understanding of the systems
+we develop as well as the systems in which we live.
+
+See [“Blacklists” and “whitelists”: a salutary warning concerning the
+prevalence of racist language in discussions of predatory
+publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) for
+further details.
+
 ## Contribution Tasks
 
 * Reporting Issues
@@ -31,7 +56,7 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 ### Reporting Issues
 
 * Make sure you have a [GitHub account](https://github.com/signup/free)
-* Submit a [Github issue](./issues) by:
+* Submit a [Github issue](https://github.com/samvera/ldp/issues/) by:
   * Clearly describing the issue
     * Provide a descriptive summary
     * Explain the expected behavior
@@ -48,7 +73,7 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
   * Please avoid working directly on the `master` branch.
   * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
 * Make sure you have added sufficient tests and documentation for your changes.
-  * Test functionality with RSpec; est features / UI with Capybara.
+  * Test functionality with RSpec; Test features / UI with Capybara.
 * Run _all_ the tests to assure nothing else was accidentally broken.
 
 ### Documenting Code
@@ -60,15 +85,11 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
   * If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
   * This work greatly increases the usability of the code base and supports the on-ramping of new committers.
   * We will all be understanding of one another's time constraints in this area.
-* YARD examples:
-  * [Hydra::Works::RemoveGenericFile](https://github.com/projecthydra-labs/hydra-works/blob/master/lib/hydra/works/services/generic_work/remove_generic_file.rb)
-  * [ActiveTriples::LocalName::Minter](https://github.com/ActiveTriples/active_triples-local_name/blob/master/lib/active_triples/local_name/minter.rb)
 * [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
 
 ### Committing changes
 
 * Make commits of logical units.
-  * Your commit should include a high level description of your work in HISTORY.textile
 * Check for unnecessary whitespace with `git diff --check` before committing.
 * Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 * If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
@@ -103,6 +124,10 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
       long to fit in 72 characters
 ```
 
+* Make sure you have added the necessary tests for your changes.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+* When you are ready to submit a pull request
+
 ### Submitting Changes
 
 * Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
@@ -125,9 +150,7 @@ We adopted [Github's Pull Request Review](https://help.github.com/articles/about
 Common checks that may occur in our repositories:
 
 1. Travis CI - where our automated tests are running
-2. Hound CI - where we check for style violations
-3. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
-4. CodeClimate - is our code remaining healthy (at least according to static code analysis)
+2. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
 
 If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
 
@@ -144,16 +167,17 @@ First, the person contributing the code is putting themselves out there. Be mind
 This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:
 
   * Does the commit message explain what is going on?
-  * Does the code changes have tests? _Not all changes need new tests, some changes are refactors_
+  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
   * Do new or changed methods, modules, and classes have documentation?
   * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
   * Does the description of the new/changed specs match your understanding of what the spec is doing?
+  * Did the Travis tests complete successfully?
 
 If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
 
 # Additional Resources
 
 * [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
 * [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
 * [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)

data/Gemfile

@@ -3,8 +3,16 @@ source 'https://rubygems.org'
 # Specify your gem's dependencies in ldp-client.gemspec
 gemspec
 
-gem 'slop', '~> 3.6' if RUBY_PLATFORM == "java"
+# gem 'slop', '~> 3.6' if RUBY_PLATFORM == "java"
 gem 'byebug', platforms: [:mri]
 gem 'activesupport'
 gem 'capybara_discoball', '~> 0.0.2'
-gem 'derby',              '~> 0.1.0'
+gem 'derby',              '~> 1.0'
+
+if ENV['RAILS_VERSION']
+  if ENV['RAILS_VERSION'] == 'edge'
+    gem 'rails', github: 'rails/rails'
+  else
+    gem 'rails', ENV['RAILS_VERSION']
+  end
+end

data/LICENSE.txt

@@ -1,4 +1,6 @@
-Copyright (c) 2013 Chris Beer
+Copyright 2013 Chris Beer
+Copyright 2014 Data Curation Experts
+Additional copyright may be held by others, as reflected in the commit history.
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

data/README.md

@@ -1,12 +1,34 @@
 # Ldp.rb
 
-[![Build Status](https://travis-ci.org/samvera/ldp.png?branch=master)](https://travis-ci.org/samvera/ldp)
+Code:
+[![Build Status](https://circleci.com/gh/samvera/ldp.svg?style=svg)](https://circleci.com/gh/samvera/ldp)
 [![Version](https://badge.fury.io/rb/ldp.png)](http://badge.fury.io/rb/ldp)
-[![Dependencies](https://gemnasium.com/samvera/ldp.png)](https://gemnasium.com/samvera/ldp)
 [![Coverage Status](https://coveralls.io/repos/github/samvera/ldp/badge.svg?branch=master)](https://coveralls.io/github/samvera/ldp?branch=master)
 
+Docs:
+[![Contribution Guidelines](http://img.shields.io/badge/CONTRIBUTING-Guidelines-blue.svg)](./CONTRIBUTING.md)
+[![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.svg)](./LICENSE.txt)
+
+Jump In: [![Slack Status](http://slack.samvera.org/badge.svg)](http://slack.samvera.org/)
+
+# What is ldp?
+
 Linked Data Platform client library for Ruby
 
+## Product Owner & Maintenance
+
+**ldp** is a Core Component of the Samvera community. The documentation for
+what this means can be found
+[here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).
+
+### Product Owner
+
+[randalldfloyd](https://github.com/randalldfloyd)
+
+# Help
+
+The Samvera community is here to help. Please see our [support guide](./SUPPORT.md).
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -39,22 +61,30 @@ orm.graph.insert([orm.resource.subject_uri, RDF::DC11.title, 'a new title'])
 # save changes
 orm.save
 ```
+## Testing:
+
+- Set Rails version you want to test against. For example:
+
+  - `export RAILS_VERSION=5.1.4`
+
+- Ensure that the correct version of Rails is installed: `bundle update`
 
-### Fedora Commons notes
-Due to some discrepancies with alpha version of Fedora Commons, you may need to do some things differently:
-* [Can't load resources from Fedora 4](https://github.com/samvera/ldp/issues/1)
-* [orm.save with an rdf:type doesn't work with Fedora 4.0.0-alpha-3](https://github.com/samvera/ldp/issues/2)
+- And run tests: `bundle exec rake rspec`
 
-## Contributing
+## Releasing
 
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+1. `bundle install`
+2. Increase the version number in `lib/ldp/version.rb`
+3. Increase the same version number in `.github_changelog_generator`
+4. Update `CHANGELOG.md` by running this command:
+  ```
+  github_changelog_generator --user samvera --project ldp --token YOUR_GITHUB_TOKEN_HERE
+  ```
+5. Commit these changes to the master branch
+6. Run `rake release`
 
-# Samvera
-This software has been developed by and is brought to you by the Hydra community.  Learn more at the
+# Acknowledgments
+This software has been developed by and is brought to you by the Samvera community.  Learn more at the
 [Samvera website](http://samvera.org)
 
 ![Samvera Logo](https://wiki.duraspace.org/download/thumbnails/87459292/samvera-fall-font2-200w.png?version=1&modificationDate=1498550535816&api=v2)

data/Rakefile

@@ -3,4 +3,4 @@ require 'rspec/core/rake_task'
 
 RSpec::Core::RakeTask.new(:spec)
 
-task :default => :spec
+task :default => :spec

data/SUPPORT.md

@@ -0,0 +1,5 @@
+If you would like to report an issue, first search [the list of issues](https://github.com/samvera/ldp/issues/) to see if someone else has already reported it, and then feel free to [create a new issue](https://github.com/samvera/ldp/issues/new).
+
+If you have questions or need help, please email [the Samvera community tech list](https://groups.google.com/forum/#!forum/samvera-tech) or stop by the #dev channel in [the Samvera community Slack team](https://wiki.duraspace.org/pages/viewpage.action?pageId=87460391#Getintouch!-Slack).
+
+You can learn more about the various Samvera communication channels on the [Get in touch!](https://wiki.duraspace.org/pages/viewpage.action?pageId=87460391) wiki page.

data/bin/ldp

@@ -17,13 +17,11 @@ rescue Ldp::NotFound
 end
 
 do_help = lambda do |x|
-
   x.command 'help' do
     run do |opts, args|
       puts opts.help
     end
   end
-
 end
 
 Slop.parse do
@@ -34,7 +32,7 @@ Slop.parse do
   end
 
   on :host=, "Host"
-  
+
   do_help.call(self)
 
   command 'get' do
@@ -92,7 +90,7 @@ Slop.parse do
     on :host=, "Host"
     do_help.call(self)
 
-    run do |opts, (path,file)|
+    run do |opts, (path, file)|
       with_error_handling do
         host = opts[:host] || ENV['LDP_HOST']
         if file.nil?
@@ -112,7 +110,7 @@ Slop.parse do
     on :host=, "Host"
     do_help.call(self)
 
-    run do |opts, (path,file)|
+    run do |opts, (path, file)|
       with_error_handling do
         host = opts[:host] || ENV['LDP_HOST']
         if file.nil?

data/ldp.gemspec

@@ -28,9 +28,12 @@ Gem::Specification.new do |spec|
   spec.add_dependency "http_logger"
   spec.add_dependency "deprecation"
   spec.add_dependency "slop"
-  spec.add_development_dependency "bundler", "~> 1.3"
+  spec.add_development_dependency "bundler", "~> 2.0"
   spec.add_development_dependency "rake"
   spec.add_development_dependency "rspec"
   spec.add_development_dependency "coveralls"
   spec.add_development_dependency "simplecov"
+  spec.add_development_dependency "rspec_junit_formatter"
+  spec.add_development_dependency 'bixby', '~> 3.0.0'
+  spec.add_development_dependency 'github_changelog_generator'
 end

data/lib/ldp/client.rb

@@ -2,7 +2,6 @@
 # LDP client for presenting an ORM on top of an LDP resource
 module Ldp
   class Client
-
     require 'ldp/client/methods'
     require 'ldp/client/prefer_headers'
     include Ldp::Client::Methods
@@ -11,14 +10,14 @@ module Ldp
 
     def initialize(*args)
       http_client, options = if args.length == 2
-        args
-      elsif args.length == 1 && args.first.is_a?(Faraday::Connection)
-        [args.first, {}]
-      elsif args.length == 1
-        [nil, args.first]
-      else
-        raise ArgumentError
-      end
+                               args
+                             elsif args.length == 1 && args.first.is_a?(Faraday::Connection)
+                               [args.first, {}]
+                             elsif args.length == 1
+                               [nil, args.first]
+                             else
+                               raise ArgumentError
+                             end
 
       @options = options
 

data/lib/ldp/client/methods.rb

@@ -3,7 +3,6 @@ require 'faraday'
 ##
 # HTTP client methods for making requests to an LDP resource and getting a response back.
 module Ldp::Client::Methods
-
   attr_reader :http
   def initialize_http_client *http_client
     if http_client.length == 1 and http_client.first.is_a? Faraday::Connection
@@ -117,36 +116,37 @@ module Ldp::Client::Methods
     resp.tap do |resp|
       unless resp.status < 400
         raise case resp.status
-          when 400
-            if resp.env.method == :head
-              # If the request was a HEAD request (which only retrieves HTTP headers),
-              # re-run it as a GET in order to retrieve a message body (which is passed on as the error message)
-              get(resp.env.url.path)
-            else
-              Ldp::BadRequest.new(resp.body)
-            end
-          when 404
-            Ldp::NotFound.new(resp.body)
-          when 409
-            Ldp::Conflict.new(resp.body)
-          when 410
-            Ldp::Gone.new(resp.body)
-          when 412
-            Ldp::PreconditionFailed.new(resp.body)
-          else
-            Ldp::HttpError.new("STATUS: #{resp.status} #{resp.body[0, 1000]}...")
-          end
+              when 400
+                if resp.env.method == :head
+                  # If the request was a HEAD request (which only retrieves HTTP headers),
+                  # re-run it as a GET in order to retrieve a message body (which is passed on as the error message)
+                  get(resp.env.url.path)
+                else
+                  Ldp::BadRequest.new(resp.body)
+                end
+              when 404
+                Ldp::NotFound.new(resp.body)
+              when 409
+                Ldp::Conflict.new(resp.body)
+              when 410
+                Ldp::Gone.new(resp.body)
+              when 412
+                Ldp::PreconditionFailed.new(resp.body)
+              else
+                Ldp::HttpError.new("STATUS: #{resp.status} #{resp.body[0, 1000]}...")
+              end
       end
     end
   end
 
   def default_headers
-    {"Content-Type"=>"text/turtle"}
+    { "Content-Type" => "text/turtle" }
   end
 
   def default_patch_headers
-    {"Content-Type"=>"application/sparql-update"}
+    { "Content-Type" => "application/sparql-update" }
   end
+
   ##
   # Some valid query paths can be mistaken for absolute URIs
   # with an alternative scheme. If the scheme isn't HTTP(S), assume