Spread2RDF

Spread2RDF is a converter for complex spreadsheets to RDF and a Ruby-internal DSL for specifying the mapping rules for this conversion.

• Supports Excel/Excelx, Google spreadsheets, OpenOffice, LibreOffice and CSV spreadsheets as input, thanks to Roo. (Currently, it's tested for Excel only. If you have problems with other spreadsheet types, raise an issue.)
• Supports many RDF serialization formats for the output, thanks to RDF.rb.
• Mapping definitions can be compiled to executables, which are runnable without having Ruby installed

Install Ruby and execute:

$ gem install spread2rdf

For a full description of available parameters, run:

$ spread2rdf --help

Write a mapping file for the spreadsheet that should be converted to RDF. Apply the mapping using the spread2rdf command-line interface or a compiled version of the mapping file.

require 'spread2rdf'

module Spread2RDF
  Schema.definition 'ProSysMod-Data' do

    namespaces(
      PSM:    'http://example.com/ProSysMod/ontology#',
      QUDT:   'http://qudt.org/schema/qudt#'
    )

    worksheet 'RDF-Export', name: :Settings do
      NS[:Base]                = cell(:B7)
      NS[:PSM_MaterialElement] = cell(:B9)
    end

    worksheet 'MaterialelementeKlassen',
              name:    :MaterialElementClasses,
              start:   :B5,
              subject: { uri: { namespace: PSM_MaterialElement },
                         type:         RDF::RDFS.Class,
                         sub_class_of: PSM.MaterialElement
              } do
      column :name, predicate: RDFS.label
      column :uri

      column :sub_class_of,     predicate: RDFS.subClassOf,
                                object:    { from: :MaterialElementClasses }
      column_block :parameter,  subject: { uri: :bnode, type: PSM.Parameter },
                                predicate: PSM.materialParameter,
                                statement: :restriction do
        column :name,        predicate: PSM.parameterName
        column :description, predicate: PSM.parameterDescription

        column :min,   predicate: PSM.parameterMinQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :exact, predicate: PSM.parameterQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :max,   predicate: PSM.parameterMaxQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :unit, object: lambda do |value|
          statements(
               [ object, QUDT.numericValue, value.to_i ],
               [ object, QUDT.unit, object_of_column(:unit) ] )
        end
      end
    end

    worksheet 'Materialelemente',
              name:   :MaterialElements,
              start:  :B5,
              subject: { uri: { namespace: PSM_MaterialElement },
                         type: PSM.MaterialElement
              } do
      column :name, predicate: RDFS.label
      column :uri

      column :modified, predicate: DC.modified,
                        object:    { datatype: XSD.date }

      column :type, predicate: RDF.type,
                    object:    { from: :MaterialElementClasses }

      column_block :parameter,  subject: { uri: :bnode, type: PSM.Parameter },
                                predicate: PSM.materialParameter do
        column :name,        predicate: PSM.parameterName
        column :description, predicate: PSM.parameterDescription

        column :min,   predicate: PSM.parameterMinQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :exact, predicate: PSM.parameterQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :max,   predicate: PSM.parameterMaxQuantity,
                       object:    { uri: :bnode, type: QUDT.QuantityValue },
                       &quantity_mapping
        column :unit, object: lambda do |value|
          statements(
               [ object, QUDT.numericValue, value.to_i ],
               [ object, QUDT.unit, object_of_column(:unit) ] )
        end
      end
    end
  end
end

A complete example file, showcasing most of the features, can be found in the examples directory.

A mapping file is a Ruby file containing a definition like this:

require 'spread2rdf'

module Spread2RDF
  Schema.definition 'Name-of-the-mapping-schema' do

  end
end

The name is purely descriptive and currently not used for anything else. The definition block contains the description of your spreadsheets schema and the conversion rules for mapping the cells to RDF.

URIs can be written in the form Namespace.suffix, where the namespace is written in uppercase. The most common namespaces like RDF, RDFS, OWL, SKOS, XSD, DC, FOAF (all predefined RDF.rb vocabularies) are available without prior declaration. Additional namespaces can be defined statically using the namespace method in the schema definition block:

module Spread2RDF
  Schema.definition 'Name-of-the-mapping-schema' do
    namespaces(
      EX:   'http://www.example.com/',
      QUDT: 'http://qudt.org/schema/qudt#'
    )
  end
end

If you want to declare a namespace dynamically, from the contents of a cell for example, an element can be added to the hash of namespaces NS. The name is given as a Ruby symbol:

worksheet 'Settings' do
  NS[:EX] = cell(:B7)
end

The schema definition block should contain a worksheet definition for every worksheet to be processed. It consists of

• the keyword worksheet,
• followed by the name of the worksheet used in the spreadsheet as a string,
• a list of named parameters (described below),
• and a block with column or column block definitions or arbitrary cell processing as in the Settings worksheet above. The order of the worksheet definitions is not significant.

If you want to refer to a worksheet (e.g. in the subject parameter) with a different name than the one used in the spreadsheet (because it contains whitespaces for example), you can define it with this parameter.

A Ruby symbol pointing to the upper-left cell of the data to be converted. Assuming the first row is a header (which is irrelevant for the conversion), the default value for this parameter is :A2.

This parameter specifies the construction of subject resources from rows. It expects a hash with further sub-parameters as its value:

• uri: Defines the rules to construct an URI for the subject. Possible values are:
  • :bnode: Construct a blank node for every subject.
  • Another hash if a full URI should be constructed with the following possible parameters:
    • column: The name of a column as a Ruby symbol, which contains the base value for the construction of an URI for a subject. In the following I will call this the subject column. The default value for this is :uri.
    • namespace: The namespace used to construct an URI for a subject by concatenation with the corresponding value of the subject column. If this is not specified, it is assumed that the subject column contains absolute URIs.
• type: The URI of the RDFS class every subject should be an element of, i.e. for every subject a rdf:type statement is produced with this URI as its object.
• sub_class_of: The URI of a RDFS class every subject should be a rdfs:subClassOf of, i.e. for every subject a rdfs:subClassOf statement is produced with this URI as its object.
• column: shortcut for the column sub-parameter of the uri parameter

Note that the rows for a subject might span multiple rows of a worksheet, for example when a column contains multiple rows with values for the same subject. The range of rows for a subject is defined by the subject column according to the following criteria:

• The first row for a subject is the row with a non-empty value in the subject column (by default the column :uri).
• The last row for a subject is the last row with an empty value in the subject column or the last row of the worksheet.

A column definition consists of

• the keyword column,
• followed by a Ruby symbol with the arbitrary name of the column,
• an optional list of named parameters (described below),
• and an optional block with custom logic (described below). The order of column definitions is significant and must correspond to the order of columns in the worksheet. For columns which should be ignored, the parameters must be omitted. Note, that the first column is defined by the start parameter of the worksheet.

The URI of the RDF property which should be used for constructing of triples for values of this column. Leaving this parameter unspecified has the same effect as setting statement to :none (see below).

This parameter specifies the construction of an object resource or value for a row and expects a hash with further sub-parameters as its value:

• language: A string or Ruby symbol with a language to be used to tag the object value of the generated triple.
• datatype: An URI to be used as the datatype for the object value of the generated triple.
• uri: Specifies the rule for the generation of a resource for the object of a triple. Currently, the following values are possible:
  • :bnode: Generate a blank node. Primarily used in conjunction with the specification of a Ruby block for custom logic (see below), where additional statements about this object are generated.
  • A Hash with a namespace key and a namespace as the value, which is used to construct an URI by concatenating it with the corresponding cell value of the column.
• type: The URI of the RDFS class every object resource should be an element of, i.e. for every object a rdf:type statement is produced with this URI as its object.
• from: Allows the specification of other data sources from which a resource is referenced with a value of the column. The graph of this data source is therefore queried for a resource with the value of the column as its rdfs:label (currently this property is hard coded, but could be made configurable). The value of this parameter can be a Hash with one or a combination of the following keys or a single Ruby symbol as a shortcut worksheet or a single string or hash as a shortcut for data_source.
  • worksheet: The name of a worksheet, whose generated output graph should be queried.
  • data_source: A single filename or an array of filenames of RDF files, which should be queried. In case of relative paths the directory of the input spreadsheet and the directories specified with the -I CLI parameter are used for the file search. Although not tested, also URLs to hosted RDF data should be possible instead of filenames, due to RDF.rb. Instead of a hash with object construction parameter, it is also possible to specify a Ruby proc with arbitrary object construction logic. This block gets the value of a cell and should return the mapped value to be used as the object of the corresponding generated triple.

This parameter allows the configuration of the triple generation. Currently, the following values are possible:

• :none: Don't generate a triple. Useful in conjunction with Ruby blocks for custom logic. Leaving the predicate parameter unspecified has the same effect.
• :inverse: Use the subject resource (from the subject column) as the object and the mapped value of a cell as the subject of the generated statement.
• :restriction: This parameter value makes only sense, when the subject is a OWL class. Instead of generating a triple of the form subject predicate object ., where subject is the resource from the subject column, predicate the value specified in the predicate parameter, and object the mapped value from the cell of a column, the following statements are generated:

  subject rdfs:subClassOf [
    rdf:type owl:Restriction ;
    owl:onProperty predicate ;
    restriction_property object
  ] .

restriction_property is owl:hasValue by default, but can be changed by giving a hash as the value of statement parameter, containing :restriction as a key and the URI of restriction property as its value.

The optional Ruby block can be used to generate further statements (or perform custom actions in general) to the values of a column. This block gets the cell value as an argument, but is executed in the context of the Cell class, so the mapped value can be accessed via the object method. It's also possible to access the value or mapped value of another column of the same row with the methods value_of_column or object_of_column. A single statement can be generated with the statement method, which expects three arguments for the subject, predicate and object. Multiple statements at once can be generated with the statements method, which takes an arbitrary number of array arguments containing the three subject, predicate and object elements of a triple.

A column block is used to define a sub sheet of a worksheet, meaning a series of columns (or further columns blocks) which are treated like a sheet, i.e. introducing subject resources, which are used as the subject of the triples generated for these columns, while the subjects itself become objects of the triples for the outer sheet (or column block).

A column block definition consists of

• the keyword column_block,
• followed by a Ruby symbol with an arbitrary name of the column block,
• an optional list of named parameters,
• and a Ruby block with column or further column block definitions. All parameters of worksheets (except start) and columns (the object parameter) can be used as parameters of a column block definition.

Templates are a way to associate a name with a Ruby block in a worksheet, for later reuse of definition blocks or mapping blocks. A template definition consists of

• the keyword template,
• followed by a name as a Ruby symbol,
• and a block. After a template definition the block can be accessed directly by using the defined name.

Example:

module Spread2RDF
  Schema.definition 'Example' do
    template :quantity_mapping do |value|
      statements(
          [ object, QUDT.numericValue, value.to_i ],
          [ object, QUDT.unit, object_of_column(:unit) ] )
    end

    worksheet 'Example sheet' do
      column :uri
      column :value, predicate: PSM.parameterMaxQuantity,
                     object:    { uri: :bnode, type: QUDT.QuantityValue },
                     &quantity_mapping
      column :unit, object: unit_mapping # unit_mapping is a predefined custom object mapping to QUDT units
    end
  end
end

Another usage for templates is the definition of a sequence of columns in a worksheet definition, by calling the include method with the template name (in this case as Ruby symbol) in a worksheet definition (at the appropriate position).

Example:

module Spread2RDF
  Schema.definition 'Example' do
    template :default_columns do
      column :name, predicate: RDFS.label
      column :uri
    end

    worksheet 'Example sheet' do
      include :default_columns
    end
  end
end

It's possible to make a schema mapping definition executable as a command-line application by placing a Schema.execute call after the schema definition in a mapping file. With that, the mapping file can be used as an executable script file, which behaves like spread2rdf with the schema mapping parameter -s implicitly set to this schema mapping, supporting all of its possible parameters (except -s obviously).

Example: A file example-mapping.s2r with the following definition

#!/usr/bin/env ruby

module Spread2RDF
  Schema.definition 'Example' do
    # ...
  end
  Schema.execute
end

can be executed as follows (assuming your system can handle the shebang line or has Ruby files associated with the ruby interpreter):

$ example-mapping.s2r example.xls

This call is equivalent to this:

$ spread2rdf -s example-mapping.s2r example.xls

An executable mapping can also be compiled to a Windows executable with the -c option of the spread2rdf command-line interface like this:

$ spread2rdf -c example-mapping.s2r

The resulting executable can then be used like the executable Ruby mapping file, but without the need of an installed Ruby, since this is compiled into the executable.

$ example-mapping.exe example.xls

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

• Marcel Otto