W3C home > Mailing lists > Public > public-linked-json@w3.org > April 2018

json-ld implementations (.NET)

From: Andrew Gibson <tinycode2@gmail.com>
Date: Sat, 7 Apr 2018 11:00:46 +0100
Message-ID: <CAPrsvnpzxdFPzHWA8d_q6cNx-EY4i5TCJCH7Ua9Mswb=V7tkdg@mail.gmail.com>
To: public-linked-json@w3.org
I'm trying to promote JSON-LD for use in APIs here in my local .NET
programming community but I'm running into a few roadblocks regarding

https://json-ld.org only lists one library for .NET - "json-ld.net", which
is maintained by Nuget (Microsoft's package manager organisation):

Furthermore, searching for json-ld in the .NET package manager, this
appears to be the only fully conforming library, though there are some
other libraries which provide utilities.

Given the above, json-ld.net appears to be the only realistic option for
using JSON-LD within .NET at the moment. However, there are some problems
with this library, including:

   1. Currently tests don't pass (simple discrepancy between http and https)
   2. The library doesn't target the most recent versions of the .NET
   3. There are annoying discrepancies between the implementation of the
   compaction algorithm in this library and the one provided in the javascript
   implementation (https://github.com/digitalbazaar/jsonld.js) although the
   spec could probably be interpreted either way.

I have been trying to engage with Nuget since the beginning of the year to
merge in basic fixes to keep things going, but I can't seem to get any
response from the maintainers even to accept pull requests (never mind
publish new versions). According to github, the repo hasn't been touched
since June 2016. Here's an example pull request I have had sitting since
Feb of this year: https://github.com/NuGet/json-ld.net/pull/24

Given that Microsoft themselves (aka Nuget) are behind this implementation,
and that it's listed on https://json-ld.org as the only implementation for
..NET, getting this version up to date would be the most compelling option
for the .NET community.

I would be happy to contribute time to keep things maintained, but I don't
work for Microsoft so I'm not sure where to turn at this stage. Is it
better to fork the library and give up on their implementation? Should the
current library be listed as "fully conforming to the offical JSON-LD
specifications" if the test suite doesn't currently pass?

Andrew Gibson
Received on Monday, 9 April 2018 08:32:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:51 UTC