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

@xpointer: change data type from token to string #280

Open
1 of 9 tasks
SJagodzinski opened this issue Dec 3, 2021 · 3 comments
Open
1 of 9 tasks

@xpointer: change data type from token to string #280

SJagodzinski opened this issue Dec 3, 2021 · 3 comments
Assignees

Comments

@SJagodzinski
Copy link
Contributor

Change data type from token to string for EAS attribute @xpointer

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. [email protected]

The issue relates to

  • EAC-CPF schema issue
  • EAC-CPF Tag Library issue
  • EAD schema issue
  • EAD Tag Library issue
  • Schema issue
  • Tag Library issue
  • Suggestions for all schemas
  • Suggestions for all Tag Libraries
  • Other

Wanted change/feature

Change data type from token to string for EAS attribute @xpointer

Context

The EAD-borrowed "xpointer" attribute should also have a type of string, not token. Here's a valid Xpointer example from the spec: "xpointer(string-range(//P,"my favorite smiley :-^)"))

@SJagodzinski
Copy link
Contributor Author

@fordmadox : This is not an EAC-CPF issue as @xpointer is not included in EAC, but it is still part of the current schema repository. Feel free to move this issue to EAD 3 if necessary

@fordmadox
Copy link
Member

No need to move to the EAD repo. I updated this issue with the 'status' issue. Technically both still work fine with xsd:token, which also allow spaces, but I think it is semantically more correct to use xsd:normalizedString for these two attributes.

See https://lists.oasis-open.org/archives/ubl/200906/msg00011.html

@fordmadox
Copy link
Member

Also, because of that above discussion around xsd:token, I think it would be fine if we keep the other 8 attributes that we currently have defined as xsd:NMTOKEN to remain that way. No major differences between the two, but it does signal that we intend them to only contain a single value rather than a series of tokens (as might be indicated if we switched to xsd:token). Still, something to discuss before the final release.

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

No branches or pull requests

2 participants