Problems with schema:studyLocation for the bioschema:Study profile

[marco-brandizi]

The current draft profile for Study says that schema:studyLocation is a recommended property. However, schema.org has MedicalStudy in its domain, and this isn't good when one wants to use bioschemas:Study to cover plant biology as well (as I'm trying to do).

Possible fixes: 1) ask schema.org to change study location or 2) use schema:contentLocation (which applies to the parent's class CreativeWork).

Another possible problem with both properties is that a location might be a simple string (ie, text should be added to its range).

[cpommier]

@bedroesb @danfaria In bioschemas:Study there is a schemas:studyLocation property that we have used so far. This property in schmas.org is used for schemas:medicalStudy, which is sligthly misleading for us. Proposition:

• in Bioschemas:Study , use schemas:place instead of studyLocation.
• Map miappe.study."Geographic location" to schemas:place

[bedroesb]

is fine for me!

[DanFaria]

Agree as well

[marco-brandizi]

So, to clarify/finalise, we're going to do this:

  study0 a bioschema:Study;
    schema:contentLocation [
      a schema:Place;
      schema:name "Cerekwica, Poland";
      schema:geo [
        a schema:GeoCoordinates;
	  schema:latitude 52.521600;
	  schema:longitude 16.659648
	]
      ]  

[AlasdairGray]

Given the description on the property contentLocation I think this is very problematic.

The location depicted or described in the content. For example, the location in a photograph or painting. I doubt that your study is depicting "Cerekwica, Poland".

The intention of reusing studyLocation is to extend the domain of the property to the general type Study being defined within the Bioschemas community as a proposal to Schema.org.

I think the description of studyLocation is closer to your intent.

The location in which the study is taking/took place.

[marco-brandizi]

@AlasdairGray, that's not one of the worst things you find in schema.org :-)

Given that that part of the description is preceded by "for example", I'd be fine with either contentLocation or studyLocation, but not so much with the latter until its domain is made more general.

Also, another sensible change might be to make studyLocation as subproperty of contentLocation.