Bump dotNetRDF from 3.1.0 to 3.1.1 in /GraphEngine

[dependabot]

Bumps dotNetRDF from 3.1.0 to 3.1.1.

Release notes

Sourced from dotNetRDF's releases.

dotNetRDF v3.1.1

This is primarily a bugfix release with one new API added to provide more control over how SPARQL results are constructed.

• FIX: Fixed a bug in the JsonLdWriter that caused an error when handling an RDF list with an unreferenced initial blank node. Thanks to @​petarhristov94 for the report and repro. (#600)
• FIX: Fixed a bug with handling multiple .GroupBy() calls in the QueryBuilder which was resulting in only the first and last expressions in the GroupBy chain to be added to the built query. Thanks to @​jiatao99 for the bug report and proposed fix. (#407)
• ENHANCEMENT: Added VDS.RDF.Query.ISparqlResultFactory to allow implementers to specify how an ISet of variable bindings are converted to an ISparqlResult instance before being passed to the client's ISparqlResultHandler. The factory instance to be used can now be set via the LeviathanQueryOptions.SparqlResultFactory property. The default implementation creates instances of the VDS.RDF.SparqlResult class. Thanks to @​jiatao99 for the suggestion. (#478)

Changelog

Sourced from dotNetRDF's changelog.

3.1.1

FIX: Fixed a bug in the JsonLdWriter that caused an error when handling an RDF list with an unreferenced initial blank node. Thanks to @​petarhristov94 for the report and repro. (#600) FIX: Fixed a bug with handling multiple .GroupBy() calls in the QueryBuilder which was resulting in only the first and last expressions in the GroupBy chain to be added to the built query. Thanks to @​jiatao99 for the bug report and proposed fix. (#407) ENHANCEMENT: Added VDS.RDF.Query.ISparqlResultFactory to allow implementers to specify how an ISet of variable bindings are converted to an ISparqlResult instance before being passed to the client's ISparqlResultHandler. The factory instance to be used can now be set via the LeviathanQueryOptions.SparqlResultFactory property. The default implementation creates instances of the VDS.RDF.SparqlResult class. Thanks to @​jiatao99 for the suggestion. (#478)

3.1

FIX: We marked a few additional APIs as obsolete. These are mostly internal/protected APIs so this change will only affect users who are extending the affected classes. The APIs that have been deprecated are those that are internally implemented using the old HttpWebRequest web APIs and all of them have alternatives that are implemented uing the more modern HttpClient API. (#88) FIX: The processing of a SPARQL zero-or-more property path was fixed to properly handle the case where there is no initial context and the path must be treated as matching all triples that match the subject and object elements of the triple pattern. Thanks to @​giacomociti for the bug report and repro. (#571) ENHANCEMENT: The BaseTripleCollection class (which is the type of the Triples property on IGraph) now supports indexing with a three-tuple of nullable INode instances as a more compact way to use the existing WithSubject(), WithSubjectPredicate() etc. methods. e.g. graph.Triples[(s, p, null)] returns an enumeration of all triples with the specified subject and predicate nodes. (#498) ENHANCEMENT: The ConfigurationLoader now supports creating NodeFactory and UriFactory instances and using them to configure Graphs and Triple Stores. It has also been updated to provide a way to set the name of a graph independetly of the BaseUri of the graph. (#500) ENHANCEMENT: Language tag validation in the NodeFactory now supports three modes. LanguageTagValidationMode.None disables langauge tag validation. LanguageTagValidationMode.Turtle validates language tags against the more relaxed definition in the Turtle 1.1 specification. LanguageTagValidationMode.WellFormed validates language tags against the stricter BCP-47 production for well-formed tags. The default validation mode is now set to LanguageTagValidationMode.Turtle. The properties NodeFactory.ValidateLanguageTags and NodeFactoryOptions.ValidateLanguageTags are both deprecated and replaced by INodeFactory.LanguageTagValidation and NodeFactoryOptions.LanguageTagValidation respectively. Thanks to @​IS4Code for their suggestions and input on this. (#565) FIX: Fix for the code that detects compressable collections which should ensure that rdf:List collections that can be represented in compressed syntax in Turtle/N3/TriG are properly compressed, and to ensure that oddly shaped lists where list nodes have multiple or missing rdf:first triples or multiple rdf:rest triples do not cause the serialisation process to throw an exception. Thanks to @​faubulous for the report (#519, #575) DOCUMENTATION: Add documentation about the way we now sign the assemblies, how that affects the use of the assemblies we distribute and our recommendation for users who need signed assemblies for full-trust situations.

3.0.1

FIX: The JSON-LD context processor has been updated to a stack overflow vulnnerability when processing remote contexts. As part of this change the default value of the RemoteContextLimit property of the JsonLdProcessorOptions has been changed from -1 (unlimited) to 10. The processor has also been modified to treat every repeat call to the same remote URL as counting towards this limit. Thanks to the dotNetRDF user who reported this.

ENHANCEMENT: The RDFa parser has been updated to be more conformant with the RDFa specs. By default the parser implements RDFa+(X)HTML processing and now passes all of the RDFa 1.1 test suite for the HTML, XHTML and XML host languages.

FIX: Fix for the JSON-LD Framing processor to correctly handle a frame with multiple @​reverse properties. Thanks to @​huibertalblas for the bug report and fix. (#556)

3.0.0

This is a new major release of dotNetRDF that introduces a number of breaking API changes. Please refer to the file v3ChangeNotes.md in this directory and/or the updated documentation (see https://dotnetrdf.org/docs/latest/user_guide/upgrading_to_3_0.html) for more details.

BREAKING: Restructuring of dotNetRDF packages. We have broken apart the monolithic dotNetRDF NuGet package in to a number of smaller packages. This has been done partly to isolate dependencies but also to break the API up into more manageable chunks. Please see the top-level README and/or the user documentation for a break-down of what each of the packages now contain. The package dotNetRdf has been changed to be a meta-package that pulls in all of the separate dotNetRDF libraries for convenience and to smooth the upgrade path from 2.x

BREAKING: Pellet support has been dropped due to lack of current open-source implementations of the Pellet server.

BREAKING: The IIS HTTP handler module (VDS.RDF.Web.*) has been dropped to remove dependencies on .NET Framework. A future release of dotNetRDF will introduce some equivalent functionality for the modern ASP.NET Core stack.

BREAKING: Support for connecting to Virtuoso via the Virtuoso client library has been dropped due to the client library requiring a dependency on .NET Framework. It is still possible to work with a Virtuoso server using the standard SPARQL connectors.

BREAKING: The global Options class has been removed and options are now specified closer to where they are used or in some cases removed entirely. Please refer to the user documentation and/or to v3ChangeNotes.md for notes on the replacements for specific Options properties.

BREAKING: Console logging of HTTP requests and responses has been removed. Please use the standard .NET HttpClient logging facility instead.

BREAKING: .NET serialization support has been removed. We recommend instead using one of the supported RDF/SPARQL syntaxes to serialize/deserialize triples, graphs, stores or SPARQL results.

BREAKING: There are some significant changes to the way that nodes can be created. At the heart of these changes is that nodes are no longer scoped to a specific graph. A node can be used to assert triples in many different graphs without having to be copied between the graphs. Much of this copying was handled internally by the implementations of the INodeFactory interface (an interface which was implemented by the Graph class amongst others). From dotNetRDF 3.0, nodes can be directly created using public constructors on the relevant classes. However the INodeFactory class remains as it provides a number of convenient functions

BREAKING: Graph Names are now specified using the Name property, not BaseUri. Prior to this release of dotNetRDF, the BaseUri property of an Graph served a dual purpose - it provided a base URI that could be used to resolve relative URI references (e.g. when creating new UriNodes in the graph); and it served as the name of the graph in an RDF dataset. With 3.0, the name of the graph can now be either an IUriNode or an IBlankNode (matching the definition of graph names in the 1.1 version of the RDF specification). This is accessed through the Name property of the IGraph interface. This property is read-only, so it can only be set as a constructor parameter. The BaseUri property remains on the IGraph interface, but it is actually now inherited from the INodeFactory interface (which IGraph extends) and is used only to resolve relative URIs when creating a new UriNode. BaseUri is a read-write property as you can (and may want to) change the effective base URI depending on the sources of RDF you are parsing to load the graph with data.

... (truncated)

Commits

• 06b26b0 Update changelog
• 7c579af Merge pull request #602 from dotnetrdf/bug/issue-600
• f3e5819 Also cover the case where the mapped usage is null
• 0a5b3c5 Repro and fix for #600
• 3da18d0 Merge pull request #599 from dotnetrdf/feature/issue-597-update-full-text-query
• 2d8a5a2 Update code to eliminate use of obsolete Lucene.NET APIs
• 4839838 Merge pull request #596 from dotnetrdf/feature/issue-478-sparql-result-set-fa...
• 2851992 Add ISparqlResultFactory and a default implementation
• 5bd9949 Merge pull request #595 from dotnetrdf/bug/issue-407-query-builder-group-by
• b24018e Test and fix for #407
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @langsamu.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[langsamu]

@dependabot merge

[dependabot]

Looks like dotNetRDF is up-to-date now, so this is no longer needed.