Hi Erik, hi all,
Aren't those properties already distinguished by the classification
statements we now have on property pages? For example:
https://www.wikidata.org/wiki/Property:P214
Defines the VIAF id to be a "unique identifier" (yes, this is somewhat
questionable modelling, since a property is not an identifier: the
*values* of the property are identifiers, but the idea should be clear).
The UI code could now use such property classifications to improve
readability. I am sure that Lydia et al. have already thought about
this, too. One could make use of more fine-grained classifications of
this type to improve the UI even further, e.g., Reasonator already
groups family relationships in the display.
Instead of using classification ("instance of" P31), one could also
introduce another property that is used on Property pages to assign them
to a "property group" (to avoid mixing UI aspects with other uses of P31
on properties). The UI can then simply group statements by the UI group
value of their property page. It would not even need to understand the
meaning of each property group -- it's enough if it has a label.
Importantly, the underlying datamodel would not change in any case, so
data consumers do not have to change their code. They can tke advantage
of the same information -- or ignore it if they don't want to present
statements in a grouped fashion.
Cheers,
Markus
On 04.04.2015 02:35, Erik Moeller wrote:
Hi all --
Have we considered separating in some way (in the UI, and possibly the
data model) properties which track identifiers in external databases vs.
properties that describe the item using Wikidata-internal links? As more
and more external identifiers are added, it's easy to get lost in them
while looking for the right property to describe an item.
We're effectively already doing this with Wikimedia identifiers by
calling them "sitelinks" and it seems like a potential logical extension
of that concept to group other kinds of external identifiers in their
own section rather than having CANTIC, BIBSYS identifiers, Freebase
identifiers or even DMOZ links mixed together with the primary
descriptors of an author or work, for example.
Thanks,
Erik
_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
