AnnotationSeries should optionally contain a target

[bendichter]

nwb-schema/core/nwb.misc.yaml

Lines 48 to 72 in 63ac845

	- neurodata_type_def: AnnotationSeries
	neurodata_type_inc: TimeSeries
	doc: Stores user annotations made during an experiment. The data[]
	field stores a text array, and timestamps are stored for each annotation (ie,
	interval=1). This is largely an alias to a standard TimeSeries storing a text
	array but that is identifiable as storing annotations in a machine-readable way.
	datasets:
	- name: data
	dtype: text
	dims:
	- num_times
	shape:
	- null
	doc: Annotations made during an experiment.
	attributes:
	- name: resolution
	dtype: float32
	value: -1.0
	doc: Smallest meaningful difference between values in data. Annotations have
	no units, so the value is fixed to -1.0.
	- name: unit
	dtype: text
	value: n/a
	doc: Base unit of measurement for working with the data. Annotations have
	no units, so the value is fixed to 'n/a'.

I am looking into creating a tutorial for AnnotationSeries. I think this is a useful type to keep around, and different enough from Event structures. However, I think it would be more useful if it was able to point to a TimeSeries. What do you all think about adding an optional link to a TimeSeries object?

[rly]

What would be the meaning/relevance of the linked TimeSeries? Can you give an example where neither the EventsTable nor the TimeIntervals table would be appropriate?

Maybe if the camera was moved starting at time A and was reset to its original position at time B, then you would want to say just the SpatialSeries from time A to time B is invalid. That's more of a time interval than an event. And in TimeIntervals, we can already link to specific TimeSeries.