Giter VIP home page Giter VIP logo

rdf-vocab's People

Contributors

acoburn avatar anarchivist avatar cdchapman avatar dazza-codes avatar dchandekstark avatar doriantaylor avatar dsisnero avatar dunn avatar gkellogg avatar jcoyne avatar lagoan avatar mjgiarlo avatar ndushay avatar wickr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rdf-vocab's Issues

Cannot `require 'rdf-vocab'`

Cannot require rdf-vocab directly, but it is present after require of linkeddata gem; i.e.

[1] pry(main)> RDF::Vocab::OA.Annotation
NameError: uninitialized constant RDF
from (pry):1:in `__pry__'
[2] pry(main)> require 'rdf-vocab'
LoadError: cannot load such file -- rdf-vocab
from (pry):2:in `require'
[3] pry(main)> RDF::Vocab::OA.Annotation
NameError: uninitialized constant RDF
from (pry):3:in `__pry__'
[4] pry(main)> require 'linkeddata'
=> true
[5] pry(main)> RDF::Vocab::OA.Annotation
=> #<RDF::Vocabulary::Term:0x3f82f113a340 URI:http://www.w3.org/ns/oa#Annotation>
[6] pry(main)> 

The entire bundle is:

$ bundle show --paths
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/addressable-2.3.8
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bcp47-0.3.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/builder-3.2.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/celluloid-0.16.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/coderay-1.1.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/coveralls-0.8.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/crack-0.4.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/diff-lcs-1.2.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/docile-1.1.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/domain_name-0.5.24
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/dotenv-2.0.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/ebnf-0.3.7
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/equivalent-xml-0.6.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/ffi-1.9.8
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/formatador-0.2.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/guard-2.12.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/guard-compat-1.2.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/guard-ctags-bundler-1.4.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/haml-4.0.6
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/hitimes-1.2.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/htmlentities-4.3.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/http-cookie-1.0.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/i18n-0.7.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/json-1.8.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/json-ld-1.1.8
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/link_header-0.0.8
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/linkeddata-1.1.11.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/listen-2.10.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/lumberjack-1.0.9
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/method_source-0.8.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/mime-types-2.4.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/mini_portile-0.6.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/nenv-0.2.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/net-http-persistent-2.9.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/netrc-0.10.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/nokogiri-1.6.6.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/notiffany-0.0.6
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/pry-0.10.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/pry-doc-0.6.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rake-10.4.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rb-fsevent-0.9.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rb-inotify-0.9.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-1.1.11
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-aggregate-repo-1.1.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-isomorphic-1.1.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-json-1.1.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-microdata-2.0.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-n3-1.1.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-rdfa-1.1.6
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-rdfxml-1.1.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-reasoner-0.2.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-tabular-0.1.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-trig-1.1.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-trix-1.1.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-turtle-1.1.6
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-vocab-0.8.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rdf-xsd-1.1.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-3.2.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-core-3.2.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-expectations-3.2.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-mocks-3.2.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/rspec-support-3.2.2
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/safe_yaml-1.0.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/shellany-0.0.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/simplecov-0.10.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/simplecov-html-0.10.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/slop-3.6.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/sparql-1.1.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/sparql-client-1.1.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/sxp-0.1.5
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/term-ansicolor-1.3.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/thor-0.19.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/tilt-2.0.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/timers-4.0.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/tins-1.3.5
/data/src/dlss/ld4l_data/annotations/triannon-client
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/unf-0.1.4
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/unf_ext-0.0.7.1
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/vcr-2.9.3
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/webmock-1.21.0
/home/user_xxx/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/yard-0.8.7.6

Is it possible to make the RDAU vocabulary less opaque?

Is it possible to make the RDAU vocabulary less opaque? ::RDF::Vocab::RDAU['/P60550'] isn't obvious what you're reasoning about in code while ::RDF::Vocab::RDAU.extent would be much better. That value is available from the triple containing "http://metadataregistry.org/uri/profile/regap/lexicalAlias". I noticed that other vocabularies are using LD patch. I'm not familiar with this (can someone suggest a good resource to learn about how it works?). Would this be a possible route to change the property names for the RDAU vocabulary?

property :"/P60550",
definition: "Relates a resource to a type, number, and measurement unit that quantify an aspect of the extent of a resource.".freeze,
"http://metadataregistry.org/uri/profile/regap/lexicalAlias": "http://rdaregistry.info/Elements/u/extent.en".freeze,
"http://metadataregistry.org/uri/profile/regap/status": "http://metadataregistry.org/uri/RegStatus/1001".freeze,
isDefinedBy: "http://rdaregistry.info/Elements/u/".freeze,
label: "has extent".freeze,
type: "http://www.w3.org/1999/02/22-rdf-syntax-ns#Property".freeze

For context

Q. Why are the IRIs unreadable?

After a great deal of discussion, the JSC (predecessor of the RDA Steering Committee) decided to use opaque IRIs for the element sets. This follows the practice established for the value vocabularies, and reflects the international environment of RDA and its translations. The RSC is also aware of the problems associated with using transparent, human-readable IRIs as a mnemonic device, especially when the properties and values of bibliographic display labels may be further developed. However, English-readable IRIs have been declared owl:sameAs to their canonical, opaque counterparts to alleviate any inconvenience this might cause for English-based linked data applications. The same facility may be developed for other languages, based on translations of RDA, in the future. The mnemonic accuracy of these IRIs is not guaranteed. http://www.rdaregistry.info/rgFAQ#faq3

RDF::Vocab::IANA['first'] no longer works

/home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/rdf-1.99.0/lib/rdf/vocabulary.rb:739:in `rescue in []': first not found in vocabulary RDF::Vocab::IANA (KeyError)

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/rdf-1.99.0/lib/rdf/vocabulary.rb:737:in `[]'

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/activefedora-aggregation-0.6.0/lib/active_fedora/orders/builder.rb:27:in `block in build'

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/activefedora-aggregation-0.6.0/lib/active_fedora/orders/builder.rb:26:in `tap'

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/activefedora-aggregation-0.6.0/lib/active_fedora/orders/builder.rb:26:in `build'

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/active-fedora-9.6.1/lib/active_fedora/associations/builder/association.rb:13:in `build'

    from /home/travis/build/projecthydra-labs/curation_concerns/vendor/bundle/ruby/2.2.0/gems/activefedora-aggregation-0.6.0/lib/active_fedora/aggregation/base_extension.rb:58:in `orders'

MARCRelator properties removed in 3.0

The vocabularies were regenerated in 5a49cb0 and MARCRelators lost all of its direct properties, so that RDF::Vocab::MARCRelators.act etc. now fail with NoMethodError:

undefined method `act' for RDF::StrictVocabulary(http://id.loc.gov/vocabulary/relators/):Class (NoMethodError)

@no-reply suggested this was likely unintentional and asked me to open an issue.

please add DCMIType vocab

from http://purl.org/dc/dcmitype/

I think I'm gonna have some delays in getting my contributor release docs together (boss is away for a week or more), or I'd do a pull request.

This should be an easy auto vocab generation. Might I suggest DCMIType as the class name?

Thanks!

gem version numbering breaks SemVer

You have a hard jump in gemspec requirements for ruby from 2.0 to 2.2 in your latest tiny release version 2.0.3

IMO according to Semantic Versioning 2.0.2 -> 2.0.3 should be non-breaking backwards compatible changes, granted this is normally scoped to your gems libs but in this case the ruby version is a considerable change. Personally I wouldn't expect an tiny change to break my install which this does, capistrano on RHEL.

I get why you did it as these older versions are EOL or soon to be but perhaps it would be better to relax version in this tiny patch's (2.0.3) ruby requirements to the ruby branch it started on or ideally re-version as 3.0.0 with the the hard requirement on ruby 2.2.0.

Update vocabularies to use language maps

This is implemented in a6d073b.

This updates numerous vocabularies to use a language-map representation for literal values, where appropriate.
Recent changes to the rdf gem (ruby-rdf/rdf@9fb42b6) allow for the use of language-maps in term definitions, for example:

property :actor,
  comment: {en: "Subproperty of as:attributedTo that identifies the primary actor"},
  domain: "https://www.w3.org/ns/activitystreams#Activity”,

Generally this change is transparent, if you use a standard accessor such as RDF::Vocab::AS.actor.comment. But, if you rely on the underlying attribute mechanism such as `RDF::Vocab::AS.actor.attributes[:comment], you will now see the language-map representation (where ‘en’, if present, will always come first)

RDF::Vocab::AS.actor.comment #=> #<RDF::Literal:0x2b84("Subproperty of as:attributedTo that identifies the primary actor"@en)>

RDF::Vocab::AS.actor.attributes[:comment] #=> {en: "Subproperty of as:attributedTo that identifies the primary actor”}

While this affects many vocabulary definitions in rdf-vocab, it adds some long missing capability to the built-in vocabulary definitions.

Without objection, this will be released in version 3.2.1 in the coming days, but as it has the potential to affect some uses of the builtin vocabularies, I wanted to call it out specifically to this group.

Contribution HOWTO

Hiya - I'm trying to determine how to add a new vocabulary to rdf/vocab with the intention of including it. What's the recommended process for doing so?

after running `rake gen_vocabs` rspec tests fail

(On the current develop branch)

I forked the repository in hopes of adding a new ontology. I added my ontology and then ran rake gen_vocabs. I ran git status and saw that a few of the vocabs were updated and a few were added. I expected that the only change would be the ontology I added. I then got an error when I tried to run the rspec tests.

I reverted all the changes, ran the vocab generator, ran the spec tests, and got the following error:

/../rdf-vocab/lib/rdf/vocab.rb:156:in `<module:Vocab>': uninitialized constant RDF::MA (NameError)
    from /.../rdf-vocab/lib/rdf/vocab.rb:6:in `<module:RDF>'
    from /.../rdf-vocab/lib/rdf/vocab.rb:5:in `<top (required)>'
    from /.../rdf-vocab/spec/spec_helper.rb:2:in `require'

want to update Bibframe vocab but it was hand edited?

The bibframe vocab is out of date; however, there is a commit 1566479 about adding a property by hand to the existing file. I'm afraid if I follow the instructions using the rake task update vocabs, it will cause more problems than it solves, especially as the hasAccompaniment property is NOT in the bibframe vocab at http://bibframe.org/vocab-list/.

Plus #26 implies that the rake task will create some additional errors.

What is the best way forward?

still not clear on how to gen vocab

Do I need to clone the rdf vocabulary or can I generate a new vocab by installing this ?

gem install rdf-vocab

rdf gen-vocab http://www.w3id.org/bot/bot.ttl
Generate Vocabulary
rdf: Must specify vocabulary UIR

rdf gen-vocab --uri http://www.w3id.org/bot/bot.ttl
Generate Vocabulary
F:/windows/tools/ruby/Ruby31-x64/lib/ruby/gems/3.1.0/gems/rdf-vocab-3.2.1/lib/rdf/vocab.rb:400:in `const_missing': uninitialized constant RDF::Vocab::BOT (NameError)
Did you mean? RDF::Vocab::WOTcd

update README to show that you need to clone this repository to generate vocab documents

release with DC vocab

The release of ruby-rdf/rdf (1.99.0) removed the DC vocab. The latest release of this gem (0.8.7.1) does not include DC vocab. The dev branch does.

Is there a release planned soon?

MODS URI incorrect?

In

rdf-vocab/lib/rdf/vocab.rb

Lines 229 to 232 in 90da023

mods: {
uri: "http://www.loc.gov/mods/rdf/v1#",
source: "http://www.loc.gov/standards/mods/modsrdf/v1/modsrdf.owl"
},
it lists the base URI for MODS as "http://www.loc.gov/mods/rdf/v1#", so we get things like the following:

irb(main):003:0> RDF::Vocab::MODS.edition
=> #<RDF::Vocabulary::Term:0x3fd764423c38 URI:http://www.loc.gov/mods/rdf/v1#edition>

But that URI 404s:

🔥  curl -IL http://www.loc.gov/mods/rdf/v1#edition
HTTP/1.1 301 Moved Permanently
Date: Tue, 09 Aug 2016 22:28:34 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Set-Cookie: __cfduid=d4fb9ff2e3ba7f2a2a149bbd69bf276601470781714; expires=Wed, 09-Aug-17 22:28:34 GMT; path=/; domain=.loc.gov; HttpOnly
Location: http://www.loc.gov/standards/mods/rdf/v1
Server: cloudflare-nginx
CF-RAY: 2cfea4527b4253cc-LAX

HTTP/1.1 404 Not Found
Date: Tue, 09 Aug 2016 22:28:34 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: __cfduid=d4fb9ff2e3ba7f2a2a149bbd69bf276601470781714; expires=Wed, 09-Aug-17 22:28:34 GMT; path=/; domain=.loc.gov; HttpOnly
Accept-Ranges: bytes
Server: cloudflare-nginx
CF-RAY: 2cfea453bb5b53cc-LAX

Is the URI base supposed to be "http://www.loc.gov/mods/modsrdf/v1#" instead? That's also where the namespace document is: http://www.loc.gov/standards/mods/modsrdf/v1/

Using https for Schema.org

RDF::Vocab::SCHEMA seems to be failing to pick anything up from sites like eBay due to the fact that they use https in their itemtypes. Can this be overridden/configured to work correctly? Note that the schema.org website now redirects to https by default.

EDIT: The FAQ has a section on http/https (https://schema.org/docs/faq.html#19).

Release

Can we get a new release with the vocabs that have been added?

Expected result with RDF+xml

Hi Gregg!

A question more than an "issue". In the docs you say RDF::vocab will work with "Turtle, JSON-LD, and HTML+RDFa" ... Does that mean that I should not expect it to work for :rdfxml? Or am I just doing it wrong? I'm limited to rdfxml because I need to do a stylesheet transform on the output but I'm not able to predict the XML namespaces in the output, so I'm hoping that I'm just missing something. If not, no worries. I can hack a solution that gets my problem solved!

Cheers!

autoload vocabularies slows 2.7

As noted in ruby-rdf/linkeddata#13, there seems to be an issue in Ruby 2.7 when using many gems, especially rdf-vocab, which use autoload. It doesn't happen when gems are included in a Gemfile and invoked using Bundler, but otherwise, there is some mysterious slow-down.

At one time, Matz was looking to deprecate autoload, but later recanted.

This issue may be resolved in Ruby core, but we may want to consider relying more on const_missing in the future.

IANA vocabulary likely to change

The issue on supporting a real vocabulary for Link Relations seems like it's heading to resolution: mnot/I-D#140. However, it seems likely that the choice of IRI will be different to the one we've used. Currently, RDF::Vocab::IANA is based on "http://www.iana.org/assignments/link-relations/", this might instead be officially "http://www.iana.org/assignments/relation#", which will cause problems for people storing link relations based on these IRIs, however I don't see much that can be done about this.

Use ld-patch to create patch changes to loaded vocabularies.

This gets around long-standing problems with several vocabularies which lead to problems every time their updated.

By creating something like the following, this can cause them to be modified when the vocabularies are loaded to be generated:

VOCABS= {
  ldp:    {
    uri: "http://www.w3.org/ns/ldp#",
    strict: false,
    patch: %{
      @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
      @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
      @prefix owl: <http://www.w3.org/2002/07/owl#>.
      @prefix : <http://www.w3.org/ns/ldp#>.
      Delete {
        :pageSortOrder rdfs:range rdf:Resource
        :Ascending a owl:Individual
        :Descending a owl:Individual
        :MemberSubject a owl:Individual
        :PreferContainment a owl:Individual
        :PreferEmptyContainer a owl:Individual
        :PreferMembership a owl:Individual
        :PreferMinimalContainer a owl:Individual
      }
      Add {
        :pageSortOrder rdfs:range rdfs:Resource
        :Ascending a owl:NamedIndividual
        :Descending a owl:NamedIndividual
        : MemberSubject a owl:NamedIndividual
        :PreferContainment a owl:NamedIndividual
        :PreferEmptyContainer a owl:NamedIndividual
        :PreferMembership a owl:NamedIndividual
        :PreferMinimalContainer a owl:NamedIndividual
      }
  }
}

Bundler: `Ref 'develop' was not found` for gkellogg/sxp-ruby

Using an up to date working copy on develop:

halfsour:rdf-vocab mark$ bundle
Fetching git://github.com/ruby-rdf/rdf.git
Fetching git://github.com/ruby-rdf/ld-patch.git
Fetching git://github.com/gkellogg/ebnf.git
Fetching git://github.com/ruby-rdf/json-ld.git
Fetching git://github.com/ruby-rdf/linkeddata.git
Fetching git://github.com/ruby-rdf/rdf-aggregate-repo.git
Fetching git://github.com/ruby-rdf/rdf-isomorphic.git
Fetching git://github.com/ruby-rdf/rdf-reasoner.git
Fetching git://github.com/ruby-rdf/rdf-spec.git
Fetching git://github.com/ruby-rdf/rdf-turtle.git
Fetching git://github.com/ruby-rdf/rdf-xsd.git
Fetching git://github.com/ruby-rdf/sparql.git
Fetching git://github.com/ruby-rdf/sparql-client.git
Fetching git://github.com/gkellogg/sxp-ruby.git
fatal: Needed a single revision
Git error: command `git rev-parse --verify develop` in directory
/Users/mark/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/cache/bundler/git/sxp-ruby-c7af729dccecf34712927d706918e604d0981ee6
has failed.
Ref 'develop' was not found. Perhaps you mispelled it?
If this error persists you could try removing the cache directory
'/Users/mark/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/cache/bundler/git/sxp-ruby-c7af729dccecf34712927d706918e604d0981ee6'

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.