Meeting minutes
<william_vw> (unsure if that's needed here)
<tl> @william_vw we all do it
<enrico> we handle the queue here
discussion about creating instances of reificationProperty class
<niklasl> https://
<AndyS> FWIW SPIN RDF is a dormant project and not active.
<doerthe> yes, right
<william_vw> niklasl yes indeed
<tl> :r rdfreifies <<( :s :p :o )>>. :r rdf:object [ .... ]
<niklasl> I think it could work it does imply that the reifier is a member of rdf:Statement, which we probably need some recommendation for.
<niklasl> Yes, as AndyS says, SHACL Rules would be valuable to look at.
<doerthe> was also my idea, but I put myself of the queue because I am reading up at the moment
<enrico> no, niklasl, reifiers are not statements!
<AndyS> OBJECT(triple term) = :o -- the function is on the tripleTerm not the reifier.
<doerthe> (after shacl inspection)
<niklasl> (A possible way using OWL infer that a specific reifier is also a classic reification: https://
<niklasl> (Something similar could be used for e.g. sh:TripleRule https://
<tl> @niklas no
<william_vw> enrico thanks, that makes sense
<niklasl> Oh no, sorry, you're right tl :)
<Zakim> tl, you wanted to ask if the rdfs:domain of an rdf:ReificationProperty is ... always a reifier?
<niklasl> +1 (IIUC) that rdf:reifies is as strong as rdf:type (a core concept)
<niklasl> To note, I don't see much use for a reifier class...
<niklasl> Not even literals denote themselves (in 1.1)...
<enrico> fight FIGHT F I G H T !!!!!
<enrico> Example: https://
<enrico> Other example: https://
<enrico> More example: https://
<enrico> UML/ORM/E-R
<niklasl> rdf:ReificationProperty rdfs:domain rdfs:Resource . # ?
<niklasl> I believe I agree that we need rdf:reifies, which is more detailed, requiring assertion and separate reification (in my words).
<william_vw> I'm also not convinced of this right now
<william_vw> (FWIW)
<doerthe> they are all grown-ups :D
<doerthe> to refine my position, I would like to have literals in subject position, but I understand why they could be dangerous. I still don't see the danger from triple terms
<niklasl> w3c/
<gb> Issue 27 Integrating different ontology designs through entailment upon triple terms (by niklasl) [use case]
<niklasl> +1 for a less-generalized RDF (Sgt RDF)
<niklasl> R-Triples ?
<tl> G-Triples and LG-Triples
<niklasl> Input restriction sounds promising.
<niklasl> Postel's law recommends outputting input syntax (and accepting but not necessarily keeping other stuff).
<william_vw> I'm signing off (lunchtime)