| Lydia_Pintscher added a comment. |
In T212564#4876174, @abian wrote:Some questions (and opinions, some of them quite uninformed):
- What should the content of labels, descriptions and aliases be for Schemas?
I'm imagining something like "humans - Schema to ensure basic structure of Items about humans"
- Should we have more than one Schema for the same explicit class?
I wouldn't want to restrict this.
- If so, how could we link all the Schemas that are affecting the same explicit class (and, for example, virtually merge them for reasoning purposes in case we want to find duplicate rules at some point)?
They could be linked from statements on the Item for the class or probably more useful on pages of related wiki projects.
- If not (my preferred option), what's the point of having manually typed labels? Schema's labels may be the corresponding class' labels, so they could be automatically retrieved.
See above.
- Should we explicitly affect more than one class from the same Schema? (At an organizational level I would say the best option is to have 1 explicit class and optionally its subclasses ↔ 1 Schema.)
I wouldn't want to prevent it.
- How should we link classes to their related Schemas in a way readable by machines? I guess these links, maybe statements, can be automatically materialized and updated. Would we do so?
Yeah probably statements later.
- Will subclasses inherit their parent classes' Schemas?
I have not thought much about that.
- What privileges should be needed to create/modify a Schema that doesn't have a special protection status? (I would say a confirmed status.)
I think especially at the beginning it will be very obscure and there is no large scale implications like with creating a new property. So I wouldn't initially restrict it. If it turns out to be a problem this should be easy enough to do.
- Should at least one label be required? (I would say yes.)
We don't require it for items. And it probably makes moving a label from one language to another more bothersome than it needs to be.
- Should at least one description be required? (I would say no.)
Agreed.
- Should different Schemas with duplicate labels in the same language be accepted? (I would say no, they shouldn't be accepted; however, if we have the option "1 explicit class and optionally its subclasses ↔ 1 Schema", then we'll have to choose the same criteria applied to Items: the duplicate combination of label+description is what we shouldn't accept.)
See above.
- Should different Schema entities be able to specify the same schema on the same classes? (I would say no, they shouldn't.)
It'd probably mean they are redundant but I'm not sure how we'd prevent it technically.
- How do we prevent one Schema from contradicting another?
I'd like to see if this actually becomes a problem. I am worried that if we make things too strict we're also breaking the system. It's a delicate balance.
They are many questions but perhaps it's good to begin to discuss them soon and, in any case, before Schemas are already working.
Jep :)
Cc: Tarrow, abian, Aklapper, Lydia_Pintscher, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, D3r1ck01, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
