Skip to content

Tags: dchandekstark/rdf

Tags

1.1.6

Toggle 1.1.6's commit message
Release 1.1.6.

* Set output encoding to UTF-8 in Writer and CLI for JRuby.
* Improve RDF generation from vocabulary terms for non-distinctive attributes.
* Date/Time/DateTime timezone updates:
  * Add #has_timezone? (#has_tz?) to Date, Time and DateTime.
  * Add #tz to Date, used for recovering timezone from lexical representation.
  * Date canonicalization does not normalize to UTC per XSD canonicalization instructions.
* Represent Literal::Time using ::DateTime instead of ::Time, as ::Time looses any declared timezone.
* Add Time#tz and Date#tz.
* Added Literal#humanize defaulting to #to_s. Special implementations for Date, Time, and DateTime.
* Update for schema.org 1.91

1.1.5.1

Toggle 1.1.5.1's commit message
Finish 1.1.5.1

* Back-off on deprecation IRIs as list subjects, as it's common to prospectively create a list to see if it's valid.

1.1.5

Toggle 1.1.5's commit message
Release 1.1.5

* schema.org version 1.9
* Add Vocabulary::Term#each_statement, #enum_for, and #to_enum.
* Fully implement Vocabulary::Term#domain_includes/#range_includes
* From Queryable#query, make sure that #query_execute is called with a block, as that's the published interface
* Simplify encoding handling of ntriples unescape (@ewout)
* Add deprecation warnings for use of Surrogate Pairs and other areas previously commented as being deprecated:
  * URI subject to list (other than rdf:nil)
  * Writer#write_graph
  * Writer#write_statements

1.1.4.3

Toggle 1.1.4.3's commit message
Release 1.1.4.3

* Updates for schema.org v1.8.

1.1.4.2

Toggle 1.1.4.2's commit message
Rekease 1.1.4.2.

* Update for schema.org 1.7 release, plus a minor update to FOAF.

1.1.4.1

Toggle 1.1.4.1's commit message
Finish 1.1.4.1.

Update for schema.org version 1.6.

1.1.4

Toggle 1.1.4's commit message
Finish 1.1.4.

* Update Reader.open documentation to indicate that using the return value as a reader is not well supported, and implementations should restrict themselves to working within a block
* Implement Node#intern using cache, so that Node("b").eql(Node("b")).
  This also allows Statement(:s, p, :o) to eql? Statement(:s, p, :o), where previously the nodes would not be the same.
* Added missing Enumerable#enum_for; it was previously just in Countable and Queryable.
* Major changes to Vocabulary:
  * Refactor Vocabulary using class instance variables.
  * Change RDF vocabulary to delegate to RDF::RDFV, allowing definitions for RDF properties, classes, datatypes along with comments and labels.
  * Implement Vocabulary::Term as subclass of URI used for vocabulary terms. This now implements Vocabulary::Term#label and Vocbulary::Term#comment in addition to Vocabulary.label_for and Vocabulary.comment_for.
  * Implement Vocabulary.to_graph to generate RDF statements for a ruby Vocabulary definition.
  * Change Vocabulary#to_graph to Vocabulary#to_enum (and #enum_for), basically doing the same thing, but avoiding emergent problems.
  * Rename HTTP vocabulary to HT, to avoid unfortunate prefix, and to be consistent with general use.
  * Describe fuller vocabulary DSL.
  * Implement Vocabulary.expand_pname.
  * Update vocabulary generation to serialize all properties (with no language or language "en")
  * Update all built-in vocabularies.
  * Use our own version of xsd RDFS vocabulary. Update RDF vocabulary.
  * Implement respond_to? and method_missing for Vocabulary::Term to create attribute accessors.
  * Move vocabulary loading from CLI method to Vocabulary.load; use for generating vocabularies.
  * Add RDF::Vocabuarly.find and .find_term to lookup URIs.
  * Remove Data-Vocabulary vocab (RDF::V).
  * Initialize vocabulary terms with the vocabulary it comes from; add Vocabulary::Term#vocab to retrieve this.
* Implement URI#pname to create a string form of URI#qname.
* Add :unique_bnodes option to writer to ensure that BNodes are uniquely serialized, in spite of any identifier used when they are initialized.

1.1.3

Toggle 1.1.3's commit message
Finish 1.1.3

1.1.2.1

Toggle 1.1.2.1's commit message
Finish 1.1.2.1.

A revision to pulled 1.1.2, which allows URI subjects and deals more sanely with initializers.

If a `values` initializer is set with an empty list, `subject` will be used as the first element in the list. Otherwise, if the list is not empty, `subject` identifies the first element of the list to which `values` are prepended yielding a new `subject`. Otherwise, if there are no initial `values`, and `subject` does not identify an existing list in `graph`, `subject` is left as is, but the list will be invalid.

1.1.2

Toggle 1.1.2's commit message
Finish 1.1.2.

* list properties/classes of strict vocabularies
* A List subject, if specified, must be a node when identifies a valid list within the graph.