ProfessionalWiki / ProfessionalWiki/WikibaseEdtf

Export does not always specify xsd:datetime for 'dumbed down' version of EDTF string

Open
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
8
Forks
8
PR merge metrics
No merged PRs in 30d

Description

In my Wikibase the valid EDTF string XXXX maps correctly maps to +0000-00-00T00:00:00Z in xsd:datetime, but without the proper datatype in the export to Blazegraph. So "+0000-00-00T00:00:00Z" should be "+0000-00-00T00:00:00Z"^^xsd:dateTime

So this TTL should have an additional ^^xsd:dateTime

wd:Q483 a wikibase:Item ;
	wdt:P19 "XXXX"^^xsd:edtf,
		"+0000-00-00T00:00:00Z" ;
	wdt:P21 "1799"^^xsd:edtf,
		"1799-01-01T00:00:00Z"^^xsd:dateTime ;

This query:

SELECT DISTINCT ?date ?type
WHERE {
  BIND(wd:Q483 AS ?item)
  ?item wdt:P19 ?date.
  BIND(datatype(?date) AS ?type)
} 

should not yield

date type
+0000-00-00T00:00:00Z xsd:string
XXXX xsd:edtf

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Q483 export and the supplied Blazegraph query, then trace where the EDTF value XXXX is converted into the +0000-00-00T00:00:00Z literal. Done means the converted literal is exported with the xsd:dateTime datatype rather than xsd:string.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
data, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.