Open tacaswell opened 4 years ago
This PR could use a description or a link to some meeting notes if there are any.
On a Pilot call @dylanmcreynolds nudged us to move forward with this. I am personally happy with it but given the importance and the cost of any future changes I think we should have at least one more meeting to pick apart the structure and the names and consider alternatives.
:+1: for @stuartcampbell's request to use this on a fully-worked example or three before we commit to it.
@tacaswell on Slack:
move "techniques" out of start document and into [its] own document class
I am in favor of proceeding on this but doing so in a separate experimental document type that can evolve quickly and make breaking changes as needed. I think @tacaswell suggested this in passing on Slack, as I tersely documented at the time, above.
There was a call on this subject today.
Things there seemed to be strong consensus on:
"literal"
or something like that).Things that might need more thought or discussion to build strong consensus:
Things that need investigation:
First off, can someone please edit the top box here and describe clearly the intent of this PR, as previously requested? Without this focus stated, the discussion is not focused.
I have heard taht NeXus has deprecated XML backends. This leads to the question of how much XML you plan to support transforming to? Namespacing is great, but there seems to be a huge debate on how or if to represent that in JSON. It seems like you could punt on some complexity if you don't intend to output XML.
That's right. HDF5 is now the only supported on-disk format for NeXus data files. The decision to drop the XML backend was between 2012 and 2014-08. (Can't find the specific decision in the notes yet.)
Provide a semantic mapping of the keys in the collected data to a known set of keys drawn from an externally owned vocabulary.