Closed ljgarcia closed 9 months ago
IMO, the big advantage of a PropertyValue in this context is, that you can use it as a structured Key-Value Pair. It basically contextualizes the value you insert. I would suggest to extend the range of those fields, which could be used to describe entities that should be used as necessary tools in the protocol:
computationalTool
The contextualization could then be used to describe the purpose or task this entity fulfills.
As an example for a computational tool, you could use STAR
as the tool for aligning gene sequences
:
{
"@type": "PropertyValue",
"name": "Sequence Alignment Software Name",
"value": "STAR",
"propertyID": "http://purl.obolibrary.org/obo/NCIT_C175896"
}
Closing as done
The components of an ISA protocol can be mapped to
labEquipment
,reagent
andcomputationalTool
and for that we need PropertyValue as a possible range.I have looked at
labEquipment
andreagent
, and it makes sense to addPropertyValue
as a possible range. They already takeDefinedTerm
as possible value and aPropertyValue
is kind of similar but for cases where theDefinedTerm
is not possible.I can do it for
computationalTool
as well but not sure how it would work. Do you have an example?For
bioSample
the preferred way would be using abioschemas:BioSample
but as it also takesDefinedTerm
I can also addPropertyValue
if you need it. We also havesample
that takesThing
as anything can be a sample of something. We can addDefinedTerm
andPropertyValue
to allow more specific information, I think it would make sense.So, from the following list, please let me know where you need
PropertyValue
:PropertyValue
would be used hereThanks!