Using jruby-1.6.3 (but it also happens with .1 and .2), I tried:

ian@rowan-15 $ gem install linkeddata
ERROR:  While executing gem ... (ArgumentError)
   undefined class/module YAML::Syck::DefaultKey

Googling around, I see that other gems have been having the same problem, but it's not clear to me what, if any, workaround I can apply locally. Suggestions welcome!

Thanks,
Ian

The README.md doesn't yet note the inclusion of rdf-vocab, i.e.
https://github.com/ruby-rdf/linkeddata/blob/develop/linkeddata.gemspec#L43

When the linkeddata gem is included in a Rails application, it somehow breaks ActiveRecord Models. I found a workaround (only include what we need instead of this whole distribution) but I wanted to report it because it very strange. I could not believe it myself at first, but its reproducible in a freshly generated app.

Observed Problem: Model-Instances are missing some properties, notably id(!) and in the case of our app also created_at and updated_at timestamps.

Reproduction:

bundle exec rails new myapp # Using rails 6.0.3.1
cd myapp
bin/rails generate model thing
bin/rails db:migrate
bin/rails runner 'Thing.create'

# everything still works, instance has `id`:
bin/rails runner 'puts Thing.first.id != nil'
# -> true

# now add the gem
echo "gem 'linkeddata'" >> Gemfile
bundle
# its broken!
bin/rails runner 'puts Thing.first.id != nil'
# -> false

# just to make sure, yes the data is correct in the db:
bin/rails runner 'puts ActiveRecord::Base.connection.execute "SELECT * from things;"'
# -> {"id"=>1, "created_at"=>"2020-06-16 15:21:56.770811", "updated_at"=>"2020-06-16 15:21:56.770811"}

The [.travis.yml](https://github.com/ruby-rdf/linkeddata/blob/develop/.travis.yml#L6) for this suggests that Ruby 1.9.3 is supported, but the latest rdf-tabular requires Ruby 2.

I'm dropping support for 1.9.3 in ActiveTriples/ActiveTriples in response to this, but wanted to make you aware of the issue.

linkedddata depends on the gem nokogumbo, at "~> 1.5". https://github.com/ruby-rdf/linkeddata/blob/develop/linkeddata.gemspec#L45

nokogumbo released a 2.0.0 in October 2018, but no app depending upon linkeddata can use them, because it insists on only 1.x.

Would it be possible to update linkeddata to allow nokogumbo 2.x? Possibly in addition to 1.x as well.

Here are the nokogumbo 2.0 release notes . It looks like there are few if any significant backwards incompat changes, so it's possible linkeddata would just work with nokogumbo 2.x as well as 1.x.

When I have 'rdf-vocab' in my Gemfile I get this message from bundler:

Your Gemfile requires gems that depend on each other, creating an infinite loop. Please remove either gem 'linkeddata' or gem 'rdf-vocab' and try again.

linkeddata 3.2.1 has a (transitive) dependency on psych 4.x. Via yaml-ld (~> 0.0) the only released version of yaml-ld is 0.0.1, which depends on psych (~> 4.0).

Psych 4.x was released with ruby 3.1, although it can be used with older rubies too.

As far as I can tell,Psych 4.x is not compatible with Rails earlier than 6.1 -- Rails 6.0 and earlier are incompatible with psych 4.x. However, linkeddata 3.2.1 requires psych 4.x, via transitive dependency. Therefore, linkeddata 3.2.1 is incompatible with Rails earlier than 6.1.

linkeddata 3.2.0 did not express an explicit dependency on psych, so was compatible with earlier Rails.

Is this intentional/desirable? Can it be fixed?

It's breaking some of our builds at eg samvera/questioning_authority#374. Bundler ought to be smart enough to resolve linkeddata to 3.2.0 and build a consistent tree.... but apparently isn't (these built-in gems are kind of a mess), and even if it was, it would be a shame to be stuck using old linkeddata.

Appreciate any thoughts from maintainers here. @gkellogg ?

gem install linkeddata
ERROR: Could not find a valid gem 'rdf' (>= 2.2.8, ~> 2.2) in any repository
ERROR: Possible alternatives: rdf

rvm 1.29.2
Ruby 2.3.3
linux ubuntu

Any idea what may cause the issue?

Hi,

we have a circleci build running and since a few days we observe that the conversion to turtle and rdf-xml format has degraded.
The conversion to ntriples works fine.

Do the following in our circleci-setup (see https://github.com/Informatievlaanderen/Data.Vlaanderen.be/blob/test/.circleci/config.yml) the following:

gem install linkeddata 
...
rdf serialize --input-format turtle --output-format rdfxml /tmp/workspace/ttl/${model}.ttl -o /tmp/workspace/voc/${model}.rdf

it installs the latest version 3.1.0 of the LinkedData gem.
In another variant of the circleci flow, we convert jsonld->*, and also here we face a performance degradation for converting to turtle and rdf-xml.
For this variant a list of 50 files is converted to nt in 1 minute, however conversion to turtle requires 90 minutes.

Is there a change in the serializers that could explain this big difference?

I tried to get a config with an older version of the rdf-turtle gem, but I did not succeeded yet. Always the latest version 3.1.0 is present. From which I assume that that version will be used to transform to turtle.

Hi,

I use the linkeddata command line tool to transform RDF files.

rdf serialize --input-format ntriples --output-format turtle subject.nt

However I do not know how to get to the specific CLI options of a specific writer. For instance:
see https://github.com/ruby-rdf/rdf-turtle/blob/master/lib/rdf/turtle/writer.rb such as --stream.

Are these propagated in some way?

Bert