Meeting minutes
<pchampin> can only stay until the end of the hour, though
<TallTed> "subject term", "predicate term", "object term", "triple term"?
<pchampin> <#pa> a schema:Person .
<pchampin> Depending on the context, I can call #pa an identifier/IRI, a node of the RDF graph, a person.
<Souri> For example, for PG audience, I could choose to say: An atomic reification associates a name with a (set of) directed, labeled edge(s).
GOFR = "Good Old-Fashioned Reification" (pronounce like "gopher"?)
<AndyS> "gopher it"
<pchampin> [] rdf:subject [].
<TallTed> perhaps instead of talking about "triple term", we could talk about rdf:triple alongside rdf:subject, rdf:predicate, rdf:object. "triple occurrence" remains hard for me to get a grip on.
<Souri> For example, for PG audience, I could choose to say: [refined a bit] Using atomic reification(s), a name may be associated with a (set of) directed, labeled edge(s).
<AndyS> https://
<enrico> https://
<AndyS> :e rdf:reifies <<(:s :p :o)>> .
<AndyS> https://
<Souri> [Simplified message to PG audience] A single atomic (well-formed?) reification (using a single rdf:reifies triple) associates a (single) name to a (single) directed, labeled edge. One can always use multiple rdf:reifies triples to implement many-to-many associations.
<pchampin> :richard :marriedTo :liz {| :e | |}.
<pchampin> :)
<niklasl> :e rdf:reifies <<( richard :marriedTo :liz )>>. # isn't this just a named edge (not even asserted)?
<pchampin> niklasl, indeed
<niklasl> (also +1 for the macro syntax for named and asserted)
<niklasl> (... with the caveat of the "sparql property path or" issue)
<AndyS> "upfront restricted syntax" is for defining semantics, and not a restriction on N-Triple, Turtle grammar.
<tl> << :e | :s :p :o >> a rdfs:Resource .
<gkellogg> () a rdfs:Resource .
<tl> tl-