Skip to content
elf Pavlik edited this page Mar 24, 2016 · 16 revisions

See

NamedNode (instead of IRI)

Pros

  • Matches BlankNode notation
  • Avoids cognitive overloading of the term -- IRI is an existing standard, with its own spec etc
  • NamedNode contains an IRI
  • existing specs and libraries: RDF-Interfaces, RDFLib.js, RDF-Ext
  • somehow similar naming - owl:NamedIndividual
  • if cases exist where a node has one or more IRIs and a value naming it IRI doesn't make sense - aka. smusing (merging) nodes
  • if daft changes to use .iri instad of .value IRI.iri looks awkward

Cons

  • Previous vote decided to go with IRI, so this would be a change/reversal
  • Potentially less clear to developers new to RDF (IRI is a known/understandable concept, NamedNode potentially less so. However, this goes for BlankNode as well, and other RDF concepts)
  • IRI is shorter
  • ruby and python use URI/IRI terminology

Other options

  • Python uses URIRef instead of named node or URI. Possibly an alternative option, IRIRef? (talk to Tim, etc)
Clone this wiki locally