Meeting 2015 12 11

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

Agenda

• Discuss results from mailing list discussion (https://lists.w3.org/Archives/Public/public-rdfjs/2015Dec/thread.html)

.type() / .nodeType() / .termType()

• reason for termType: could also be list

• node, term relation? term is a superclass of node.

• difference on node and term properties?

• termType() seems to be more used in the RDF community (r2rml)

• the spec doesn't enforce a specific prototype chain

• values (exact) which are given back ("BlankNode", "blankNode", "bnode", "bNode", "blanknode" ?)

  • discussed aspects:
    • length of value because of typing
    • same strings as interface description
    • historical stuff

.why() / .graph()

• value should definitely be a Node, so it can be a Named Node or Blank Node
• ".graphName" => might be too restricting
• ".graph()"

Next Steps

Possible layers of the interface:

1. (datamodel) core: Triples / Quads / building blocks
2. (generation) r/w : Sources / Sinks
3. (manipulation): lists, prefix map, graph (graph or store? can there be multiple graphs (with quads described) in a store?)

Issue 1:

• closed

Issue 2:

• what happens when you clone?
• maybe create a document with suggested properties

Issue 4: What is the scope of the spec.

• Goal, Mission statement: The focus on this first low level interface is to find a minimal API for access of RDF data which can be shared by JS Libraries. (which JS Librarieries)

Issue 5: .value() on blankNode how to represent

• .value() comes without any ? or _:
• for a version with _: and ? look for Issues 7

Issue 6: .toString() ?

• Is usefull for Debugging
• the group might come back later on this
• pointer to specify the other links

Tasks

• mention "no prototype chain" in the spec
• new issues on answer of .termType() => Ruben
• document about additional properties => @bergos
• issue 4 (mission statement) => Michael
• issue 5 (change spec) => @bergos
• issue 6 (change spec) => @bergos