Property talk:P1060

From Wikidata
Jump to navigation Jump to search

Documentation

disease transmission process
process by which a pathogen is transmitted, equivalent to "transmitted by" in the relation ontology http://purl.obolibrary.org/obo/RO_0002451
DescriptionHow a pathogen is transmitted. Follows the pathogen transmission ontology from OBO.
Representspathogen transmission (Q525512)
Data typeItem
Domain
According to this template: types of disease (Q12136)
According to statements in the property:
disease (Q12136)
When possible, data should only be stored as statements
Allowed valuestypes of pathogen transmission (Q525512) (note: this should be moved to the property statements)
Exampleinfluenza (Q2840)airborne transmission (Q11986959)
chickenpox (Q44727)contact transmission (Q15304512)
droplet infection (Q871752)
SourceScientific publications (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P1060 (Q47461895)
Lists
Proposal discussionProposal discussion
Current uses
Total332
Main statement32798.5% of uses
Qualifier30.9% of uses
Reference20.6% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “disease (Q12136): item must contain property “subclass of (P279)” with classes “disease (Q12136)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1060#Type Q12136, SPARQL
Value type “pathogen transmission (Q525512): This property should use items as value that contain property “subclass of (P279)”. On these, the value for subclass of (P279) should be an item that uses subclass of (P279) with value pathogen transmission (Q525512) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1060#Value type Q525512, SPARQL



Examples[edit]

These examples were used during the discussion:

  • transmission process = (im not sure in this case? maybe:vehicle-borne ingestion)
  • tuberkolosis
  • transmission process = airborne

Comments[edit]

You should also consider that parasite and vector could be used as independent statements and not as qualifiers. This would increase compatibility with the current specifications of SemanticWeb. Another consideration is that the vector could also be included in transmission process by creating further subclass of (P279)-items in the ontological tree:

or even:

  • transmission process = female anopheles borne
Having parasite and vector as independent statements might also make it easier to add suitable inverse properties to the parasite and vector items. For instance, Triatoma dimidiata (Q3015504) is one of several bugs transmitting Chagas disease (Q649558). --Daniel Mietchen (talk) 02:04, 8 January 2014 (UTC)[reply]

Ontology[edit]

This following represents the ontology of pathogen transmission as suggested by the Open Biological and Biomedical Ontology Foundry Ontologies (Q4117183):

Pathogen transmission class hierarchy


Sorry for not reading this page and not discussing here, but I've introduced horizontal transmission (Q4254955) and vertical transmission (Q2834381) into the tree. And I added some items. As a result, this is the current tree:
Bold items are changed from former state. --Okkn (talk) 18:52, 17 August 2016 (UTC)[reply]

How to specify objects of this property[edit]

As I mentioned in the property proposal discussion, I am concerned about the hierarchy of this ontology, in that it attempts to recapitulate sub-branches of the biological taxonomy tree in order to describe the details of the transmission process. I still think that a qualifier that identifies the species would be much more appropriate here, but @Emw: disagrees, on the basis that W3C standards don't natively support n-ary relationships. I think this is misguided, because: A, Wikidata has qualifiers and has/will have a standard way to "reify" them into RDF (see mw:Wikidata/Development/RDF#Statements_with_qualifiers), and B, sometimes, as in this example, qualifiers really are the "right" way to do something, and anything else would be a bad fit. The currently proposed set of allowed values is bad because they are classes as opposed to individuals, which does not make sense. We have an ongoing discussion about that in Wikidata:Project_chat#Question_about_classes.2C_and_.27instance_of.27_vs_.27subclass.27, but at least in the case of sex or gender (P21), which also takes a class as its object, it makes sense to think of the subject as being an instance of (for example) the "female" class. In this case, on the other hand, it wouldn't make sense to say that a given disease is an instance of, for example, "vehicle-borne fomite". So, I don't understand how this class hierarchy would translate into meaningful data on which inferences could be drawn, automatically (as opposed to ad-hoc queries). Klortho (talk) 06:55, 9 January 2014 (UTC)[reply]

Regarding the Pathogen Transmission ontology -- (aka transmission process) -- I am the developer for this ontology, I have moved it to GitHub (transmission_process.obo and trans.owl files in: https://github.com/DiseaseOntology/HumanDiseaseOntology/tree/master/src/ontology, to enable us to look at this further, to expand the term, as outlined in the above discussion, to define this in the context of Wikidata qualifiers. Lschriml.