Should we use a JSON-LD reference for relative URLs?

[iherman]

Both the current JSON and RDF mappings use the following:

URL expansion behaviour of relative URLs shall be consistent with Section 6.3 IRI Expansion in [JSON-LD-API]. The base URL provides the URL against which relative URLs from annotated tabular data are resolved. The base URL shall be that of the source CSV file.

The reference leads to: http://www.w3.org/TR/json-ld-api/#iri-expansion which is a fairly complex algorithm, take care of issues around compact URIs, prefixes, suffixes, etc. This seems to be an overkill for what we need it for, and will really scare people away. We should find a simpler reference for relative URIs (one of the RFC-s I guess).

This is related to issue #91.

[JeniT]

This should be (and is, I believe) handled in the metadata document, not in the conversion specs. This issue also relates to #191.

The right reference about relative URL resolution is probably the URL spec.

[JeniT]

Resolved at Feb F2F. We will summarise the expansion processing that is necessary for our purposes, and say that it is intended to be consistent with JSON-LD IRI expansion. We do have some restrictions on what IRIs can be used, eg we don't allow blank node syntax.