Fwd: RDF 1.1. xsd 1.1 change in meaning of years -1 and before? [Was Re: Starting on issue 55 and 32]

Sorry had only replied to Ethan.


-------- Forwarded Message --------
Subject: RDF 1.1. xsd 1.1 change in meaning of years -1 and before? [Was 
Re: Starting on issue 55 and 32]
Date: Tue, 28 May 2019 18:17:45 +0200
From: Jerven Tjalling Bolleman <Jerven.Bolleman@sib.swiss>
Reply-To: Jerven.Bolleman@sib.swiss
Organisation: SIB Swiss Institute of Bioinformatics
To: Ethan Gruber <ewg4xuva@gmail.com>

Hi Ethan,

Interesting point that I had not considered (of course I prefer my dates 
after 1970 ;) and have nightmares about gregorian calendars and 
leapyears before the year 1.
And as usual the kraken has risen out of the depths of time :)

So it seems that in RDF1.1. the normative reference is XMLSCHEMA11-1 
(https://www.w3.org/TR/xmlschema11-2/)

Which notes in https://www.w3.org/TR/xmlschema11-2/#dt-dt-7PropMod that

"In this version of this specification, two changes are made in order to 
agree with existing usage. First, ·year· is permitted to have the value 
zero. Second, the interpretation of ·year· values is changed 
accordingly: a ·year· value of zero represents 1 BCE, −1 represents 2 
BCE, etc. This representation simplifies interval arithmetic and 
leap-year calculation for dates before the common era (which may be why 
astronomers and others interested in such calculations with the 
proleptic Gregorian calendar have adopted it), and is consistent with 
the current edition of [ISO 8601]."

If anyone remembers if this was discussed in the RDF1.1/SPARQL1.1 days 
could you please add to https://github.com/w3c/sparql-12/issues/93.

Regards,
Jerven



On 2019-05-28 15:45, Ethan Gruber wrote:
> Related to these two, I created
> https://github.com/w3c/sparql-12/issues/93 to discuss long-running
> problems with consistently encoding BC dates.
> 
> On Mon, May 27, 2019 at 9:34 AM Jerven Bolleman
> <jerven.bolleman@sib.swiss> wrote:
> 
>> Dear Community,
>> 
>> Welcome and let's get started :) We have a see of ideas and
>> proposals to
>> work with, thanks to everyone who made an issue!
>> 
>> Now the ideas need to turn into reality, which means turn them into
>> a
>> number of mini specs that are implementable (i.e. have a good
>> covering test suite, decent corner case coverage and reasonably
>> formal).
>> 
>> As a learning exercise I would like to start with issue
>> https://github.com/w3c/sparql-12/issues/55
>> and
>> https://github.com/w3c/sparql-12/issues/32
>> 
>> These are extending the number of inbuilt functions to match the
>> XPath
>> 3.1 specifications.
>> 
>> What I want to do is have both a spec and a test suite for
>> implementers.
>> This is a training issue for us to discover how we can work together
>> and
>> encourage implementations that our wider community can build upon.
>> 
>> For those who are interested in following along I will be working
>> on it this Wednesday 1st of May 12:00 UTC time. I registered a
>> gitter.im [1]
>> chat room on which anyone interested can join
>> https://gitter.im/sparql-12/community#
>> 
>> Of course this is not the only issue of interest and I encourage
>> everyone to start on helping specifying their topic of interest.
>> 
>> Besides specifications, we are very interested in best practices
>> regarding SPARQL on the public web. I would like to start
>> with using some of the things we have done for sparql.uniprot.org
>> [2] as
>> a template (hoping you agree they are best practices ;)
>> 
>> Regards,
>> Jerven
> 
> 
> Links:
> ------
> [1] http://gitter.im
> [2] http://sparql.uniprot.org

-- 
Jerven Tjalling Bolleman
SIB | Swiss Institute of Bioinformatics
CMU - 1, rue Michel Servet - 1211 Geneva 4
t: +41 22 379 58 85 - f: +41 22 379 58 58
Jerven.Bolleman@sib.swiss - http://www.sib.swiss

Received on Wednesday, 29 May 2019 09:52:40 UTC