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

Release constraints on name #449

Closed
marcenacp opened this issue Jan 17, 2024 · 2 comments
Closed

Release constraints on name #449

marcenacp opened this issue Jan 17, 2024 · 2 comments

Comments

@marcenacp
Copy link
Contributor

Names are IDs with specific constraints (no white space, no special character). These constraints should be lowered except for basic checks (e.g., no line return?).

@goeffthomas
Copy link
Contributor

@marcenacp Curious about the name length requirement as well. Is that a hard requirement of one of our dependencies? Curious if other data providers have expressed similar concerns.

@marcenacp
Copy link
Contributor Author

Notes on offline conversations we had with Pierre, Omar and Stanze:

  • Name of dataset: no constraint (not even on length).
  • Name of RecordSet/Field/etc: https://www.w3.org/TR/xml/#sec-common-syn. Names are supposed to be IDs, so by convention we should use @id (standard in JSON-LD). Currently we picked the CSVW standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants