Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
add Technology/Technique attribute to Science Dataset #1425
as per discussion with the Bioschema group at the Rothamsted meeting.
How about calling it "measurementTechnique" (applies to types: Dataset, DataDownload, perhaps DataCatalog for small homogenous collections, value: Text or (perhaps?) URL).
measurementTechnique: "A description of a technique or technology used in a Dataset (or DataDownload, DataCatalog), corresponding to the method used for measuring the variable(s) which may be described with one or more variableMeasured properties. "
For example, if variable measured is: molecule concentration, measurementTechnique could be: "mass spectrometry" or "nmr spectroscopy" or "colorimetry" or "immunofluorescence". If the variableMeasured is "depression rating", the
If we have several variableMeasured properties recorded for some given data object, we have the problem of being clear which technique goes with which variableMeasured. Since variableMeasured allows for a PropertyValue structure as its value, suggest that we allow measurementTechnique to optionally be attached at that level, so that the grouping detail is preserved.
Talking with Natasha Noy, there's still a problem maybe. We discussed adding URL range to variableMeasured for well known codes to be cited by URL/URI identifiers.
In this case it may be that well known URLs for variableMeasured are best represented via sameAs on the PropertyValue, even if that is a bit verbose. Not clear if these 3 conditions will be common.
Jumping in late: a W3C/OGC working group has been developing a revised version of the 'Semantic Sensor Network' ontology . A core vocabulary has been factored out, known as SOSA (Sensors, Observations, Samples and Actuators) which is intended to have a scope suitable for schema.org . In place of 'variableMeasured' SOSA has sosa:observedProperty, whose value is expected to be a sosa:ObservableProperty 
ObservableProperty is intended to name a property-type, like color, mass, temperature, which appears to match the description on https://developers.google.com/search/docs/data-types/datasets .
So, two items of feedback:
 http://w3c.github.io/sdw/ssn/ - also includes alignments with OGC O&M, OBOE, prov-o
@dr-shorthair PropertyValue holds both sides. The "name" and "value". Where the "name" can use the propertyId or description fields ... and the value uses the value field (along with other fields if needed like maxValue and valueReference. And we allow structure for both sides, or it can be just freeform text string. Your ObservablePropety is just the "name" side and not the "value" side, correct ? I.E. "the height of a tree" and not also its "12 feet".
UPDATE: @dr-shorthair Actually, I think I just found the "value" side in SOSA, looks like Observations are made and values are stored in a Result http://w3c.github.io/sdw/ssn/#SOSAResult ??
I prepared a fairly complete mapping from SSN/SOSA to schema.org a couple of years ago - see https://github.com/w3c/sdw/blob/gh-pages/ssn/rdf/sosa-sdo-mapping.ttl