David Boas

sounds good. Thanks @rob-luke

@samuelpowell This looks good to me. Stephen's changes to the measurementList and measurementLists all looks good. It doesn't capture clearly that the requirement is that only one should be present....

I like the idea of having the validator enforce that only one be present. BUT This could be annoying for the user, many of whom will not be skilled enough...

Your logic convinces me Sam 😊 From: Sam Powell ***@***.***> Date: Thursday, September 19, 2024 at 4:18 AM To: fNIRS/snirf ***@***.***> Cc: Boas, David ***@***.***>, Mention ***@***.***> Subject: Re: [fNIRS/snirf]...

@samuelpowell how do you suggest the specification language indicate that only one be present? Presently they both indicate that they are required if the other is not present. I am...

Sam is right. The validator could handle this and throw an error if both are present. We could clarify the language in the spec to indicate to the human that...

@samuelpowell and @sstucker , @sreekanthkura7 pointed out to me that he is pretty sure that Stephen's validator is using the coding in the [SNIRF data format summary](https://github.com/fNIRS/snirf/blob/master/snirf_specification.md#snirf-data-format-summary). He needs to...

I like this idea. @sreekanthkura7 is meeting with the maintainers next Monday. He will review with them and then likely implement this and move forward on implementing the validator.

@Edouard2laire , I was just looking at this coordinate system requirement in the BIDS spec today. It goes in the coordsystem.json file. I agree this would be good to get...

@HanBnrd , I think the suggestion is making [/nirs(i)/probe/coordinateSystem](https://github.com/fNIRS/snirf/blob/master/snirf_specification.md#nirsiprobecoordinatesystem) required if 3D positions is present. And recommending, but not requiring [/nirs(i)/probe/landmarkPos3D](https://github.com/fNIRS/snirf/blob/master/snirf_specification.md#nirsiprobelandmarkpos3d). One can always using 'other' for the coordinateSystem and...