We do have the "Quote" property (P1683) which has monolingual text
datatype. You could certainly put free text in the value for this property
and add this to a reference or even use it as a qualifier.
On Wed, Apr 1, 2015 at 9:54 AM, Daniel Kinzler <daniel.kinzler(a)wikimedia.de>
Am 01.04.2015 um 09:20 schrieb Valentine Charles:
-Cultural Heritage data have most of the time a
will find lot of relevant free text information.
The structured property
inside you will find mostly free- text. I
couldn't find a similar
Wikidata but there is something similar in
Dbpedia. Is it something you
planning to introduce or have you made the
decision to exclude any
infromation from Wikidata for now.
Free-form text is not machine-readable. Coding semi-structured information
very common in archives etc, but makes the data very hard to export,
and query. Free text fields should be used only for things that are
text, such as a state motto.
I think the need to encode things in free-form fields arose mostly from
rigid data schemas. If there's no dedicated field for something, just
info into the text field. Such fields turn into kitchen sinks that contain
hodge podge of different kinds of information.
With Wikidata, there should be no need for this, since you can just create
use any properties you might be missing. That does mean though that wile
importing, you have to somehow extract the relevant information from the
text. That effort has to be done at some point, if the data is to become
-While I was looking for painting in Wikidata I
also noticed the absence
information related to the size/dimension of the
most of the time present in Cultural Heritage
data. Is it something
interested in or has it been omitted
We don't support units of measurement yet, and without these, it's not
possible to give the dimension. We hope to finally change this over the
couple of months.
-Then the last question is about values in
different languages for a
property. How do you indicate the language in
Wikidata? Are you using a
attribute or something similar?
xml:lang would be used in the XML/RDF export (and lang in the HTML
Internally, the language would be a string associated with the "language"
a JSON structure. But neither fact is really relevant to the data model on
Most properties (most data types) are language agnostic. Quantities,
time values, etc, do not have any notion of language. The only datatype for
properties that supports a language code is "monolingual text" (a pair of
language code + text). This data type is used sparingly, since usually,
for internationalized naming and description is covered by the labels,
descriptions, and aliases associated with a data item.
Labels, descriptions, and aliases are not "properties" about which
statements would be made in the context of the data item. Instead, they are
editorial attributes. They are fully internationalized, and intended to
display, disambiguation, and search in as many languages as possible.
For example, Q219831 has labels (and descriptions) in many languages:
* nl: De Nachtwacht (schilderij van Rembrandt van Rijn)
* de: Die Nachtwache (Gemälde von Rembrandt)
* en: The Night Watch (painting by Rembrandt van Rijn)
* ru: Ночной дозор (картина)
So, when the painting is referenced elsewhere, a label (and description)
shown in the user's language. Internationalized statements/properties are
Senior Software Developer
Gesellschaft zur Förderung Freien Wissens e.V.
Wikidata-l mailing list