Hi,
Thanks for the clarification. This is an ultra-low feature, and as I said:
this is only an [optional] feature for importing from data from sql or
similar and not for humans.
Regards.
On Fri, Jan 4, 2013 at 8:50 AM, Denny Vrandečić <
denny.vrandecic(a)wikimedia.de> wrote:
The problem is is that 20120101 is ambiguous --
it could be either the
year 20120101, or the 1st of January of last year.
Whereas admittedly it is more likely to be the latter, it might be
considered a bit too much magic to guess 20000101 as the first of
January of 2000 and 20000000 as "in 20 Mio years".
ISO8601 states that the notation without hypen separators should be
avoided. Therefor, if there is no strong opposition to it, I would put a
low priority on this kind of magic.
(On the other hand, if you make a patch that deals with this ambiguity
magically, I would merge it)
(By the way, when importing the data through the API the magic of the
parser would not happen -- i.e. it would require you to write it down in
exactly the kind of format we specify The magic parser is only there to
support humans, not machines).
2013/1/3 Dennis Tobar <dennis.tobar(a)gmail.com>
Hi,
I'm testing the timestamp format and I note that doesn't support date in
ISO basic format (ISO 8601), as is documented in MS SQL Server pages:
yyyymmdd[1][2] (yes, without separator string).
The expected value to 20120101 is Jan 1, 2012, but the script returns
this json
{
"time": "+00020120101-01-01T00:00:00Z",
"precision": 9,
"before": 0,
"after": 0,
"utcoffset": "+00:00",
"calendar": "http://wikidata.org/id/Q1985727"
}
This is my little feedback, thinking about importing some data from
sqlserver to any repository.
Regards
[1]
http://msdn.microsoft.com/en-us/library/aa226054(v=sql.80).aspx
[2]
http://en.wikipedia.org/wiki/ISO_8601#Calendar_dates
On Thu, Jan 3, 2013 at 1:11 PM, Denny Vrandečić <
denny.vrandecic(a)wikimedia.de> wrote:
Hi all,
continuing from last weeks data values discussion, I would like to
invite comments on the following prototypes for understanding points of
time and points on Earth.
<http://simia.net/valueparser/time.html>
<http://simia.net/valueparser/coordinate.html>
What it currently does not do is:
* i18n (it's in the code, but not properly exposed yet)
* enable dates like "Date of birth: 437-436 BC"
Working on both still, but I'd like to have a first round of feedback.
Happy 2013,
Denny
--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 |
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Dennis Tobar Calderón
Ingeniero en Informática UTEM
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 |
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Dennis Tobar Calderón
Ingeniero en Informática UTEM
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org