Finish 2.1.0

Author: gkellogg

.coveralls.yml

@@ -0,0 +1 @@
+repo_token: U92RjLkZjzwi3VDahukmbTXemdvLS1oEs

.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+# This workflow runs continuous CI across different versions of ruby on all branches and pull requests to develop.
+
+name: CI
+on:
+  push:
+    branches: [ '**' ]
+  pull_request:
+    branches: [ develop ]
+  workflow_dispatch:
+
+jobs:
+  tests:
+    name: Ruby ${{ matrix.ruby }}
+    if: "contains(github.event.commits[0].message, '[ci skip]') == false"
+    runs-on: ubuntu-latest
+    env:
+      CI: true
+      ALLOW_FAILURES: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'jruby' }}
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby:
+          - 2.6
+          - 2.7
+          - 3.0
+          - 3.1
+          - ruby-head
+          - jruby
+    steps:
+      - name: Clone repository
+        uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - name: Install dependencies
+        run: bundle install --jobs 4 --retry 3
+      - name: Run tests
+        run: ruby --version; bundle exec rspec spec || $ALLOW_FAILURES
+ 

.gitignore

@@ -11,4 +11,7 @@ Gemfile.lock
 *.sw?
 benchmark/
 
-.storage
+.storage
+coverage
+test-output
+report

CHANGELOG.md

@@ -82,3 +82,8 @@
    - Ships with a limited server "Lamprey"
    - Note: 0.1.0 was a gem containing only an `RDF::Vocabulary`, this
      has been moved to `rdf-vocab`
+ 
+0.2.1 
+------
+ - Deprecates Ruby < 2.6, supports Ruby 3.
+ - Updated dependencies.

CONSTRAINED_BY.md

@@ -6,9 +6,9 @@ This file documents constraints imposed by `RDF::LDP`, `Rack:LDP` middleware, an
 RDF Types
 ---------
 
-The `RDF::LDP` core does not set types for resources. Complying with [LDP 4.3.1.2](http://www.w3.org/TR/ldp/#h-ldprs-gen-atleast1rdftype) is left to the client (or the server implementer). Interaction models are expressed as Link headers, and the client may infer rdf:types in accordance with the specification.
+The `RDF::LDP` core does not set types for resources. Complying with [LDP 4.3.1.2](https://www.w3.org/TR/ldp/#h-ldprs-gen-atleast1rdftype) is left to the client (or the server implementer). Interaction models are expressed as Link headers, and the client may infer rdf:types in accordance with the specification.
 
-Similarly, we do not enforce the recommendation of [LDP 5.2.1.3](http://www.w3.org/TR/ldp/#h-ldpc-nordfcontainertypes) for containers not to have type ` rdf:Bag`, `rdf:Seq` or `rdf:List`. This is left to the client (or server implementer) to manage.
+Similarly, we do not enforce the recommendation of [LDP 5.2.1.3](https://www.w3.org/TR/ldp/#h-ldpc-nordfcontainertypes) for containers not to have type ` rdf:Bag`, `rdf:Seq` or `rdf:List`. This is left to the client (or server implementer) to manage.
 
 POST/PUT Requests
 ------------------
@@ -47,7 +47,7 @@ For Indirect Contianers with an `ldp:insertedContentRelation` other than `ldp:Me
 Named Graphs
 -------------
 
-Serializations supporting quads are allowed in POST and PUT requests. Graph names are ignored, and the file is treated as a single graph representing the resource. This behavior is seen as in compliance with [4.2.4.1](http://www.w3.org/TR/ldp/#h-ldpr-put-replaceall).
+Serializations supporting quads are allowed in POST and PUT requests. Graph names are ignored, and the file is treated as a single graph representing the resource. This behavior is seen as in compliance with [4.2.4.1](https://www.w3.org/TR/ldp/#h-ldpr-put-replaceall).
 
 HTTP PATCH
 -----------
@@ -56,4 +56,4 @@ We currently support HTTP PATCH with the LDPatch and SPARQL Update formats. PATC
 
 ----
 
-Linking to this document fulfills [Section 4.2.1.6](http://www.w3.org/TR/ldp#h-ldpr-gen-pubclireqs) of the LDP specification. Implementers of servers based on `RDF::LDP` and `Rack::LDP` are advised to create their own documents to clarify how these constraints effect their own services.
+Linking to this document fulfills [Section 4.2.1.6](https://www.w3.org/TR/ldp#h-ldpr-gen-pubclireqs) of the LDP specification. Implementers of servers based on `RDF::LDP` and `Rack::LDP` are advised to create their own documents to clarify how these constraints effect their own services.

CREDITS

@@ -0,0 +1 @@
+* Gregg Kellogg <gregg@greggkellogg.net>

Gemfile

@@ -52,4 +52,6 @@ end
 group :test do
   gem 'equivalent-xml'
   gem 'rake'
+  gem 'simplecov',      '~> 0.16', platforms: :mri
+  gem 'coveralls',      '~> 0.8', '>= 0.8.23',  platforms: :mri
 end

README.md

@@ -1,7 +1,9 @@
 RDF::LDP
 ========
-
-[![Build Status](https://travis-ci.org/ruby-rdf/rdf-ldp.svg?branch=develop)](https://travis-ci.org/ruby-rdf/rdf-ldp)
+[![Gem Version](https://badge.fury.io/rb/rdf-ldp.png)](https://badge.fury.io/rb/rdf-ldp)
+[![Build Status](https://github.com/ruby-rdf/rdf-ldp/workflows/CI/badge.svg?branch=develop)](https://github.com/ruby-rdf/rdf-ldp/actions?query=workflow%3ACI)
+[![Coverage Status](https://coveralls.io/repos/ruby-rdf/rdf-ldp/badge.svg)](https://coveralls.io/github/ruby-rdf/rdf-ldp)
+[![Gitter chat](https://badges.gitter.im/ruby-rdf/rdf.png)](https://gitter.im/ruby-rdf/rdf)
 
 Server-side support for Linked Data Platform (LDP) with RDF.rb. To get started
 with LDP, see the [LDP Primer](https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-primer/ldp-primer.html).
@@ -89,7 +91,7 @@ app = proc do |env|
   # The `Rack::LDP` middleware marhsalls the request to the resource, builds the response,
   # and handles conneg for RDF serializations (when the body is an `RDF::LDP::RDFSource`).
   #
-  # @see http://www.rubydoc.info/github/rack/rack/master/file/SPEC#The_Response
+  # @see https://www.rubydoc.info/github/rack/rack/master/file/SPEC#The_Response
   
   [200, {}, RDF::LDP::Resource.find(RDF::URI(env['REQUEST_URI']), repository)]
 end
@@ -148,10 +150,33 @@ gem to run the suite and generate the tests.
 RDF.rb Compatibility
 --------------------------
 
-As of version 2.0, this software depends on RDF.rb 3.1 or greater.
+As of version 2.1, this software depends on RDF.rb 3.2 or greater.
 
+## Contributing
 
-License
-========
+This repository uses [Git Flow](https://github.com/nvie/gitflow) to mange development and release activity. All submissions _must_ be on a feature branch based on the _develop_ branch to ease staging and integration.
+
+* Do your best to adhere to the existing coding conventions and idioms.
+* Don't use hard tabs, and don't leave trailing whitespace on any line.
+  Before committing, run `git diff --check` to make sure of this.
+* Do document every method you add using [YARD][] annotations. Read the
+  [tutorial][YARD-GS] or just look at the existing code for examples.
+* Don't touch the `.gemspec` or `VERSION` files. If you need to change them,
+  do so on your private branch only.
+* Do feel free to add yourself to the `CREDITS` file and the
+  corresponding list in the the `README`. Alphabetical order applies.
+* Don't touch the `AUTHORS` file. If your contributions are significant
+  enough, be assured we will eventually add you in there.
+* Do note that in order for us to merge any non-trivial changes (as a rule
+  of thumb, additions larger than about 15 lines of code), we need an
+  explicit [public domain dedication][PDD] on record from you,
+  which you will be asked to agree to on the first commit to a repo within the organization.
+  Note that the agreement applies to all repos in the [Ruby RDF](https://github.com/ruby-rdf/) organization.
+
+## License
 
 This software is released under a public domain waiver (Unlicense).
+
+[YARD]:             https://yardoc.org/
+[YARD-GS]:          https://rubydoc.info/docs/yard/file/docs/GettingStarted.md
+[PDD]:              https://unlicense.org/#unlicensing-contributions

UNLICENSE

@@ -21,4 +21,4 @@ OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
 ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
 OTHER DEALINGS IN THE SOFTWARE.
 
-For more information, please refer to <http://unlicense.org/>
+For more information, please refer to <https://unlicense.org/>

VERSION

@@ -1 +1 @@
-2.0.1
+2.1.0