reassessing BehavioralProtocol #536
Description
goal: have a Linked Data representation for behavioral protocols that provide a recipe for others, allows for semantic integration between protocols through tagged components, can be extended with in-depth execution information (for provenance from subject -> file)
Current schema properties and their problem:
- describedIn: linked object array (1-N) of type DOI, File or WebResource; references external sources where the behavioral protocol was described in; how accurate does this need to fit?
- description: narrative text (should be written as recipe); information often not sufficient to rebuilt/understand the structure of the task/protocol
- internalIdentifier: string that is used to abbreviate the behavioral protocol in the data; needs to be removed because this varies for each execution
- name: user defined string; however often names are not very good, maybe make this a composite of provided structured information?
- stimulation: linked object array (1-N) of type StimulationApproach or StimulationTechnique; can provide the collective list of stimulation procedures but not their order or meaning
- stimulusType: linked object array (1-N) of type AuditoryStimulusType, ElectricalStimulusType, GustatoryStimulusType, OlfactoryStimulusType, OpticalStimulusType, TactileStimulusType or VisualStimulusType; same issue as for stimulation