Open SJagodzinski opened 2 years ago
@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
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
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.
Change data type from token to string for EAS attribute
@xpointer
Creator of issue
The issue relates to
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 :-^)"))