On 10/17/14 2:00 PM, Kingsley Idehen wrote:
On 10/17/14 11:48 AM, Pat Hayes wrote:On Oct 17, 2014, at 6:34 AM, Kingsley Idehen <[email protected]> wrote:But endorsing, signing, etc. are all things that attach to transaction time rather than valid time. They are all things done to the document (to the data) rather than things that the data talks about. (Except in those cases where what the data talks about is those very signings, endorsings, etc., but that is exactly where the distinction becomes pointless since the valid and transaction times coincide.)On 10/17/14 12:00 AM, Pat Hayes wrote:Kingsley, greetings.It is important to keep a clear distinction between what temporal DB calls valid time and transaction time. T-time is when the record was inserted into the databese or when it was created.Yes, certainly.This is important, basically, for internal accounting and maintenance of the DB itself.Yes.V-time is the time being referred to in the data. So for example, if Bill and Jane are married on 01012014 and this fact gets inserted into a record of marriages on 05012014, there are two times involved, and these are the valid and transaction times respectively.Yes.What you are talking about, when you suggest using reification and dates of documents, is transaction time, not valid time.If this was based solely on the world view of the RDF Reification Ontology [1], then yes, but I have an extended Ontology [2] that adds addition properties to the Statement Class. These extensions arose so that statements in a document could be endorsed and signed etc..You point me to your ontology, below, where it defines endorsement as a "claim used to describe statements". Exactly: it describes the *statement*, not what the statement is talking about. I can endorse in 2014 a statement made in 2013 about a house purchase deed transfer which took place in 2011. The actual event was the transfer, which is not a document and not an endorement of a document, but an actual event in the world, which these documents refer to. Which is why I, in 2014, might have to pay fines to the IRS for taxes not paid in 2011.This is why reification is the wrong tool to be using to describe valid times. Valid times are extra arguments to the relations in the data, or related to events described in the data; transaction times are arguments to relations between times and the data itself.PatI don't believe I am suggesting the use of reification for valid times. I am indicating (hopefully) that what's described in a document and the mechanism of description (RDF statements, using [in my case] TURTLE notation) can be collectively used to establish fact from fiction, so to speak.A marriage certificate is a document comprised of claims that reflect a reality comprised of temporal relations -- just like any other document that describes events e.g., ISWC 2014.Here's the kind of document to which my thoughts apply, in regards to this matter. For instance, I've made a claim about when this event starts and ends, and claimed that some entity (referred to as <#ISWC2014Organization>) has endorsed the statements in question etc.:## Nanotation Start ## <> a <http://rdfs.org/sioc/ns#Post> ;<http://purl.org/dc/terms/created> "2014-10-17T13:10+05:00"^^xsd:dateTime;<https://twitter.com/hashtag/features#this> [ a Person; foaf:mbox <mailto:[email protected]> ], <http://kingsley.idehen.net/dataspace/person#this> ;<http://xmlns.com/foaf/0.1/primaryTopic> <https://twitter.com/hashtage/Reification>;<http://xmlns.com/foaf/0.1/topic> <#ISWC2014>, <#StartStatement> . <#ISWC2014> a <http://purl.org/NET/c4dm/event.owl#Event> ; <http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014" ;<http://www.w3.org/2004/02/skos/core#altLabel> "International Semantic Web Conference 2014"; <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#beginsAtDateTime> "2014-10-19T08:00-01:00"^^xsd:dateTime; <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#endsAtDateTime> "2014-10-23T17:00-01:00"^^xsd:dateTime;<http://www.w3.org/2007/05/powder-s#describedby> <>. <#ISWC2014EventStartStatement> a <http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement> ;<http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014EventStartStatement" ; <http://www.w3.org/2004/02/skos/core#prefLabel> "ISWC2014 Event Start Statement" ;<http://www.w3.org/1999/02/22-rdf-syntax-ns#subject> <#ISWC2014>;<http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate> <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#beginsAtDateTime> ; <http://www.w3.org/1999/02/22-rdf-syntax-ns#object> "2014-10-19T08:00-01:00"^^xsd:dateTime ;<http://www.w3.org/2007/05/powder-s#describedby> <>. <#ISWC2014StatementEndorsementExample><http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014StatementEndorsementExample" ; <http://www.w3.org/2004/02/skos/core#prefLabel> "ISWC 2014 Statement Endorsement Example" ;a <http://www.openlinksw.com/schemas/reification#Endorsement> ;<http://www.openlinksw.com/schemas/reification#endorser> <#ISWC2014Organization> ;<http://www.w3.org/2007/05/powder-s#describedby> <>. <https://twitter.com/hashtag/features#this> rdfs:isDefinedBy <http://linkeddata.uriburner.com/c/8CAOF4> . ## Nanotation End ##To conclude, if my view point remain unclear (I believe I understand your concerns), then a tweak of what's represented above will be mutually beneficial, at the very least :)Kingsley
Correction to the example above, especially we are trying to work through an example:
## Nanotation Start ## ## Added missing statement that states ## ## <#ISWC2014StatementEndorsementExample>## <http://www.openlinksw.com/schemas/reification#endorsement> <#ISWC2014EventStartStatement> .
<> a <http://rdfs.org/sioc/ns#Post> ; <http://purl.org/dc/terms/created> "2014-10-17T13:10+05:00"^^xsd:dateTime; <https://twitter.com/hashtag/features#this> [ a Person; <http://xmlns.com/foaf/0.1/mbox> <mailto:[email protected]> <http://xmlns.com/foaf/0.1/name> "Pay Hayes"], <http://kingsley.idehen.net/dataspace/person#this> ;<http://xmlns.com/foaf/0.1/primaryTopic> <https://twitter.com/hashtage/Reification>;
<http://xmlns.com/foaf/0.1/topic> <#ISWC2014>, <#StartStatement> . <#ISWC2014> a <http://purl.org/NET/c4dm/event.owl#Event> ; <http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014" ;<http://www.w3.org/2004/02/skos/core#altLabel> "International Semantic Web Conference 2014"; <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#beginsAtDateTime> "2014-10-19T08:00-01:00"^^xsd:dateTime; <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#endsAtDateTime> "2014-10-23T17:00-01:00"^^xsd:dateTime;
<http://www.w3.org/2007/05/powder-s#describedby> <>. <#ISWC2014EventStartStatement> a <http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement> ; <http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014EventStartStatement" ;<http://www.w3.org/2004/02/skos/core#prefLabel> "ISWC2014 Event Start Statement" ;
<http://www.w3.org/1999/02/22-rdf-syntax-ns#subject> <#ISWC2014>;<http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate> <http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#beginsAtDateTime> ; <http://www.w3.org/1999/02/22-rdf-syntax-ns#object> "2014-10-19T08:00-01:00"^^xsd:dateTime ;
<http://www.w3.org/2007/05/powder-s#describedby> <>. <#ISWC2014StatementEndorsementExample> a <http://www.openlinksw.com/schemas/reification#Endorsement> ;<http://www.w3.org/2000/01/rdf-schema#label> "ISWC2014StatementEndorsementExample" ; <http://www.w3.org/2004/02/skos/core#prefLabel> "ISWC 2014 Statement Endorsement Example" ; <http://www.openlinksw.com/schemas/reification#endorser> <#ISWC2014Organization> ; <http://www.openlinksw.com/schemas/reification#endorsement> <#ISWC2014EventStartStatement> ;
<http://www.w3.org/2007/05/powder-s#describedby> <>. <https://twitter.com/hashtag/features#this><http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <http://linkeddata.uriburner.com/c/8CAOF4> .
## Nanotation End ## Links: [1] http://linkeddata.uriburner.com/c/8FWUGK -- old version[2] http://linkeddata.uriburner.com/c/9BBPGMPD -- page that revealed missing statement (i.e., missing relation that indicates what's being endorsed).
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
smime.p7s
Description: S/MIME Cryptographic Signature
