Skip to content
Michael Luggen edited this page Dec 29, 2015 · 2 revisions

Previous meetings are in https://github.com/rdfjs/representation-task-force/wiki

Agenda

Pull request 1

.why or graph

  • in a quad, you just need one slot
  • same thing could be in same way as s / p / o
  • .why and .graph are probably the same
  • drawback of .why: rdflib.js has to change
  • We ask the rdfjs mailing list about .why or .graph
    • elaborate on use cases, see what goes in there, to determine most logical naming

distinction IRI / named node

  • IRI/URL/URI: things that start "http://…", they are strings for @timbl
    • but in some code, IRI has pieces
    • RDF said "named node = IRI", but that's a shortcut
  • developers know what they are anyway
  • "named node" makes more sense because there's also "blank node"
    • make API more understandable than documentation
    • .symbol might be too obscure
    • NamedNode got no objections as it is only about naming
  • it is consistent with blankNode
  • we should probably contact the RDF1.1 group to clarify on this

other issues

checking the type of a node

  • .value as uniform access vs. having .iri .string .?
  • how to check the type if we only have .value
  • termType / nodeType ?
  • if we use .value, we might use .type as well
    • but .type is more abstract than .value
  • value should be a String
    • maybe peformance issue
    • but canonical can be faster

introduction of higher level abstractions?

  • might make sense to have something for lists
    • but it is a low-level library, we should focus on pure triples/quads first
    • maybe add them to util
    • create issue for this
    • dependend on which rdf standard nquads turtles?

Varia

  • Wednesday will be always the last call for changing the meeting time on the respective friday.

# Tasks

  • send out mail about .why/.graph + timeout => Ruben
  • send out mail about .type/.termType/.nodeType + timeout => Ruben
  • Add issue for lists / utils => Michael