The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
An editor has requested the community to provide input on "Unifying GO activities and enzyme articles" via the Requests for comment (RFC) process. This is the discussion page regarding the issue.
If you have an opinion regarding this issue, feel free to comment below. Thank you!
THIS RFC IS CLOSED. Please do NOT vote nor add comments.
Most (but not all) binary duplicates on EC enzyme number (P591) are caused by different bots that create different entries for the same enzyme activity: one from the various Wikipedia bots that generate flat articles (such as en:Thymidine-triphosphatase, EC 3.6.1.39, Thymidine-triphosphatase (Q7799624)) and one from a huge import from Gene ontology (GO) at some point in the history of Wikidata (thymidine-triphosphatase activity (Q22320779)). These describe the same thing and should be merged globally across the site. In fake bot-speak that would be:
Before moving on to the bot request, however, I figured that it is a good idea to RFC this since this is expected to be a huge move. And bot requests need justification anyway. --Artoria2e5 (talk) 15:01, 12 June 2019 (UTC)[reply]
Support. This matter already exists for Wikidata items of drugs and drug classes. I am working on a project to adjust Wikidata biomedical taxonomy. All contributors are invited to join the project. --Csisc (talk) 13:23, 19 June 2019 (UTC)[reply]
CommentSupport Conceptually I'm very supportive of this plan, but would like to see what an example merged item would look like in practice. Just want to make sure I understand how this would impact User:ProteinBoxBot, which I help manage. @Artoria2e5:, can you perform one merge as an example? (I'd do it myself, but I'm not confident I wouldn't mess it up or do it in a different way than you envision.) Best, Andrew Su (talk) 18:59, 20 June 2019 (UTC)[reply]
Technically what is classified is usually concrete objects of the real world, for example my car, or my stomach, are examples of the « car » or « stomach » concepts. « My stomach » is then with no ambiguity an instance of « stomach », and could nether be a subclass. The « instance of » statements should be translated as « is an example of », and « subclass of » statements as « are examples of ». For example « human stomach(s) » are example of « stomach(s) », hence « subclass of » is the right property. Here, enzymes are examples of proteins, so the right property is « subclass of ». There is an exception to this rule, as so called « meta-classes ». I tried to summary these in User:TomT0m/Classification. See also en:Is-a (on the ambiguity of the « is a » relationship, which is why there is both instance of and subclass of) and/or en:type-token distinction for a philosophical perspective and en:metaclass (semantic web) for metaclasses. author TomT0m / talk page21:09, 22 June 2019 (UTC)[reply]
Thanks for the example, Artoria2e5. Yup, that looks fine from the ProteinBoxBot perspective. I think the reference to "imported from Wikipedia" is not necessary when we have a more authoritative source already there, but not a big deal either. Best, Andrew Su (talk) 19:10, 24 June 2019 (UTC)[reply]
Comment Please also add the qualifier "mapping relation type"--->"exact match" with the merged entries. This would make it possible to distinguish them from items of specific proteins, and we could then remove the distinctiveness criterion. --SCIdude (talk) 07:48, 29 August 2019 (UTC)[reply]
final comment: I see. There is no way to get a list of pairs to merge except via manual inspection, and then you can merge manually as well... --SCIdude (talk) 09:55, 2 September 2019 (UTC)[reply]
Oppose. Actually, I'm now against this. The concepts "enzyme family" and "molecular function" are too different. Most refuting is that the activity item has an "exact match" statement which gets falsified by the merge. Also, proteins "have" the activity/function through molecular function (P680) and the proposal would merge subject and object of such a statement, e.g. how to state "xyz-group of methyltransferases have methyltransferase activity"? The mentioned problems like inst-of enzyme should be dealt with separately from merging making them inst-of enzyme family. Finally note WD should reflect reality (through imported data) not Wikipedia article design which has its own demands. --SCIdude (talk) 16:10, 2 September 2019 (UTC)[reply]
Wikidata:Requests for comment/Unifying GO activities and enzyme articles
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
If you have an opinion regarding this issue, feel free to comment below. Thank you!
THIS RFC IS CLOSED. Please do NOT vote nor add comments.
Most (but not all) binary duplicates on EC enzyme number (P591) are caused by different bots that create different entries for the same enzyme activity: one from the various Wikipedia bots that generate flat articles (such as en:Thymidine-triphosphatase, EC 3.6.1.39, Thymidine-triphosphatase (Q7799624)) and one from a huge import from Gene ontology (GO) at some point in the history of Wikidata (thymidine-triphosphatase activity (Q22320779)). These describe the same thing and should be merged globally across the site. In fake bot-speak that would be:
.-
, leave it for now.Before moving on to the bot request, however, I figured that it is a good idea to RFC this since this is expected to be a huge move. And bot requests need justification anyway. --Artoria2e5 (talk) 15:01, 12 June 2019 (UTC)[reply]
Notified participants of WikiProject Medicine ChristianKl ❪✉❫ 07:43, 19 June 2019 (UTC)[reply]Comments
[edit]CommentSupport Conceptually I'm very supportive of this plan, but would like to see what an example merged item would look like in practice. Just want to make sure I understand how this would impact User:ProteinBoxBot, which I help manage. @Artoria2e5:, can you perform one merge as an example? (I'd do it myself, but I'm not confident I wouldn't mess it up or do it in a different way than you envision.) Best, Andrew Su (talk) 18:59, 20 June 2019 (UTC)[reply]: Support. Please more of these fixes. --SCIdude (talk) 13:50, 29 July 2019 (UTC)[reply]@Artoria2e5: what happens next? Are you still prepared to merge these entries? The issue is constantly getting in my editing path. --SCIdude (talk) 07:36, 29 August 2019 (UTC)[reply]final comment:I see. There is no way to get a list of pairs to merge except via manual inspection, and then you can merge manually as well... --SCIdude (talk) 09:55, 2 September 2019 (UTC)[reply]Info I propose to close this RfC as no consensus after 31 January 2024. Please comment if you don’t agree. --Emu (talk) 20:17, 13 January 2024 (UTC)[reply]
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.
Navigation menu
Search