| daniel edited the task description. (Show Details) |
EDIT DETAILS
The person needs to be identified by a plain text name, to satisfy legal requirements. In addition, a URL (resp URI) can be given to uniquely identify the person (or legal entity).
So we need a new Wikibase datatype that covers them all so statements can be made using the same property.
Our current thinking: This would be a new datatype representing a smart URI - internally it'd always be a URIOur current thinking: This would be a new datatype representing a plain text name and an optional URI. The user interface should be "smart" about well known types of URLs - for example, it could have a selector that offers Commons user pages, Flickr user pages and a bunch of others as a drop-down.
Whether the URL would be part of the main data value, or whether it should be provided as a qualifier, is not yet decided. andIf we add nice UI handling for a small number of special cases.use qualifiers, For example it could have a selector that offers Commons user pages,a more complex widget is needed that allows the main value and the relevant qualifier to be edited together. Flickr user pages and a bunch of others as a drop-down.It seems difficult to integrate this nicely with the generic display and editing UI for qualifiers.
...
* a person represented by an item on WikidataThe person needs to be identified by a plain text name, to satisfy legal requirements. In addition, a URL (resp URI) can be given to uniquely identify the person (or legal entity).
So we need a new Wikibase datatype that covers them all so statements can be made using the same property.
Our current thinking: This would be a new datatype representing a smart URI - internally it'd always be a URIOur current thinking: This would be a new datatype representing a plain text name and an optional URI. The user interface should be "smart" about well known types of URLs - for example, it could have a selector that offers Commons user pages, Flickr user pages and a bunch of others as a drop-down.
Whether the URL would be part of the main data value, or whether it should be provided as a qualifier, is not yet decided. andIf we add nice UI handling for a small number of special cases.use qualifiers, For example it could have a selector that offers Commons user pages,a more complex widget is needed that allows the main value and the relevant qualifier to be edited together. Flickr user pages and a bunch of others as a drop-down.It seems difficult to integrate this nicely with the generic display and editing UI for qualifiers.
TASK DETAIL
EMAIL PREFERENCES
To: daniel
Cc: thiemowmde, Ladsgroup, Liuxinyu970226, Pigsonthewing, Bugreporter, Jan_Dittrich, Josve05a, Sadads, Pokefan95, gerritbot, DannyH, Micru, intracer, mkroetzsch, Aklapper, daniel, Steinsplitter, Lydia_Pintscher, D3r1ck01, Izno, Wikidata-bugs, aude, El_Grafo, Mbch331
Cc: thiemowmde, Ladsgroup, Liuxinyu970226, Pigsonthewing, Bugreporter, Jan_Dittrich, Josve05a, Sadads, Pokefan95, gerritbot, DannyH, Micru, intracer, mkroetzsch, Aklapper, daniel, Steinsplitter, Lydia_Pintscher, D3r1ck01, Izno, Wikidata-bugs, aude, El_Grafo, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
