docmentation: how to create new vocabs, and langage-tagged strings in vocabs about rdf HOT 3 CLOSED

You're right that the DSL doesn't really handle language-tagged literals. The point of the DSL, though, is to create sub-classes of RDF::Vocabulary (and the DSL is essentially just using the class-methods from RDF::Vocabulary and RDF::Vocabulary::Term). It's most easily done using RDF::Vocabulary::Writer from a graph, which is available through the rdf CLI. For example, from the rdf-vocab Rakefile

cmd = "bundle exec rdf"
if v[:patch]
  File.open("lib/rdf/vocab/#{id}.rb_p", "w") {|f| f.write v[:patch]}
  cmd += " patch --patch-file lib/rdf/vocab/#{id}.rb_p"
end
cmd += " serialize --uri '#{v[:uri]}' --output-format vocabulary --ordered"
cmd += " --module-name #{v.fetch(:module_name, "RDF::Vocab")}"
cmd += " --class-name #{v[:class_name] ? v[:class_name] : id.to_s.upcase}"
cmd += " --strict" if v.fetch(:strict, true)
cmd += " --noDoc"
cmd += " --extra #{URI.encode_www_form_component v[:extra].to_json}" if v[:extra]
cmd += " -o lib/rdf/vocab/#{id}.rb_t"
cmd += " '" + v.fetch(:source, v[:uri]) + "'"
puts "  #{cmd}"

The DSL for, say .property, instantiates a new RDF::Vocabulary::Term, where there are some heuristics to turn option entries into IRI keys and values. String or Symbol values that look like IRIs are used to create an RDF::URI, otherwise, they are either Date, DateTime, Integer, Decimal, Double, Boolean, or Literal. There isn't anything specific to create a language-tagged literal, but of course, the property option values could be instances of RDF::Literal, instead.

Given the way RDF::Vocabulary::Term#attribute_value is implemented, we could interpret an Hash value to be something like a language map. But, that would complicate many other places which use vocabularies and expect simple literal values for accessors such as #comment and #label.

In summary, there may be some ripple effects to things which use vocabularies, but something like you suggest is probably feasible, but ambitious.

from rdf.

@wu-lee I added support to this to the develop branch, and will also update the rdf-vocab representation. As this is potentially disruptive (but shouldn't be), I'll give the [email protected] mailing list an opportunity to object before releasing to RubyGems. If that happens, it will end up falling back to an option, at lest until the next dot release. It does affect many vocabularies in rdf-vocab.

from rdf.

Thank you for this. I'll investigate when I get a moment.

from rdf.