Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Values that are node names #57

Closed
VisLab opened this issue Apr 25, 2022 · 1 comment · Fixed by #157
Closed

Values that are node names #57

VisLab opened this issue Apr 25, 2022 · 1 comment · Fixed by #157
Labels
hed 3 HED 3-specific issues validation Tag validation issues

Comments

@VisLab
Copy link
Member

VisLab commented Apr 25, 2022

A clarification has been made in the spec that allows values to be node names. This is in the process of being incorporated into the hed validator.

Definitions are a special case: Definition names cannot be node names. However, Definitions can also take values:

(Definition/My-def/# .... ) The values substituted for # can be node names in Def/My-def/Red or (Def-expand/My-def/Red .... )

@happy5214 happy5214 added this to the 4.0.0 milestone Apr 27, 2022
@happy5214 happy5214 added hed 3 HED 3-specific issues validation Tag validation issues labels May 3, 2022
@happy5214
Copy link
Member

As evidenced by the fact that the test added in 4795a96 had to be skipped in order to be committed, this issue was not fixed in v3.7.0.

@happy5214 happy5214 removed this from the 4.0.0 milestone May 26, 2023
@happy5214 happy5214 linked a pull request Jul 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hed 3 HED 3-specific issues validation Tag validation issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants