Last modified: 2014-10-13 13:28:04 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T73992, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71992 - JSON should (optionally) contain full URIs for referenced external entities
JSON should (optionally) contain full URIs for referenced external entities
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Wikidata bugs
u=dev c=backend p=0
:
Depends on:
Blocks: 42063
  Show dependency treegraph
 
Reported: 2014-10-13 11:42 UTC by Daniel Kinzler
Modified: 2014-10-13 13:28 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel Kinzler 2014-10-13 11:42:07 UTC
Wikidata contains a variety of properties that refer to external resources using standard identifiers for such resources, e.g. ISBN, VIAF, MusicBrainz, GND, etc. it should be possible for clients to resolve these to URIs automatically, either by including the URI expansion in the JSON representation of the respective Statement or DataValue, or by at least including the necessary mappings elsewhere in the JSON document.

Currently, Wikibase knows nothing about the interpretation of external IDs, which are stored and interpreted as plain StringValues. In order to provide URI expansion, a new DataType would be needed on top of StringValue, which would contain the URI pattern and perhaps regular expressions for validating and/or normalizing the IDs. This additional information would need to be recorded in the respective property definitions (or in a separate vocabulary definition which could be re-used by multiple properties).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links