Wikidata:Property proposal/associated shape
Jump to navigation
Jump to search
associated shape[edit]
Originally proposed at Wikidata:Property proposal/Generic
Withdrawn
Description | shape expression described in item |
---|---|
Represents | Shape Expressions (Q29377880) |
Data type | ⧼datatypes-type-EntitySchema⧽ (not available yet) |
Domain | Q29377880 |
Allowed values | E-entities |
Example 1 | <new item> → E10 |
Example 2 | <another new item> → E15 |
Example 3 | <new item> → E21 |
Number of IDs in source | one for each schema |
Expected completeness | eventually complete (Q21873974) |
Robot and gadget jobs | could be generated automatically |
Motivation[edit]
Given the current implementation of e-entities, this allows to describe and query schemes in a structured way. (Add your motivation for this property here.) --- Jura 08:08, 2 June 2019 (UTC)
Discussion[edit]
- Wait According to posters on the wikidata-l list, viz. [1], there is a standard RDF serialization for ShapeExpressions. It should be better either to include the RDF triples of these serializations directly within WDQS to describe a shape entity; or to load them into an associated triplestore, that could service federated queries from WDQS; rather than to try to keep and then maintain a parallel set of Q-items for shape expressions, that would expect each shape expression to be described in detail in duplicate. ShapeExpressions are supposed to describe themselves. That is a job we should let them do. Jheald (talk) 16:54, 2 June 2019 (UTC)
- Currently that is not possible at Wikidata. As any format used in Wikibase, they have numerous possibilities and options, but at implementation stage, one needs to decide which ones to use.
Apparently we can already link schemes without this, thus I'm withdrawing it. --- Jura 11:00, 14 June 2019 (UTC) - @User:Jheald: I quoted you at phab:T271065. --SCIdude (talk) 17:51, 3 January 2021 (UTC)
- Currently that is not possible at Wikidata. As any format used in Wikibase, they have numerous possibilities and options, but at implementation stage, one needs to decide which ones to use.