- From: Aymeric Brisse <aymeric.brisse@gmail.com>
- Date: Thu, 19 Dec 2019 00:25:23 +0100
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: W3C Ruby RDF mailing list <public-rdf-ruby@w3.org>
- Message-ID: <CANURzhi0uCJY29CFwbPLz-GSDMeGDF9O+VDcyf+SefZrVmvr_A@mail.gmail.com>
Thanks for the update Gregg, I will test it soon. On Tue, Dec 17, 2019, 20:56 Gregg Kellogg <gregg@greggkellogg.net> wrote: > As announced on this list in August, the 3.1 release removes support for > Ruby versions before 2.4 and full support for Ruby 2.7. > > As part of this release, there are numerous internal updates to manage > changes in the way Ruby 2.7 handles hash conversion to keyword arguments. > When using Ruby 2.7, this sometimes requires that calls to a method where > the first argument can be a hash, and there is are keyword arguments, or a > **options hash need to have the first argument enclused in curly braces > ({}). This mostly affects calls to RDF::Queryable#query and RDF::Query.new, > but there are some other cases. It shouldn’t affect anyone not using Ruby > 2.7. > > Along with this release is the json-ld gem, also at 3.1, which fully > supports the JSON-LD 1.1 Candidate Recommendation [1][2][3]. People > depending on the output of framing may notice that the top-level object no > longer uses @graph; this can be changed using an option, or by explicitly > setting processingMode to “json-ld-1.0”. > > The Distiller [4] has been updated with the latest releases, and > consolidated documentation for all gems can be found there. > > Gregg Kellogg > gregg@greggkellogg.net > > [1] https://www.w3.org/TR/json-ld11/ > [2] https://www.w3.org/TR/json-ld11-api/ > [3] https://www.w3.org/TR/json-ld11-framing/ > [4] http://rdf.greggkellogg.net/distiller > > >
Received on Wednesday, 18 December 2019 23:25:34 UTC