You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a file with attributes like "#affected+injured+dineo+2017" - starting with a digit which are not recognized as valid tag. Due to this, the file is marked as not having hxl tags even if it had other valid tags&attributes.
Q: do we need to change the pattern to support attributes that starts with digit?
note: this tag "#affected+injured+dineo+y2017" is valid
The text was updated successfully, but these errors were encountered:
We can talk about changing the syntax. HXL was originally designed to use the same identifier syntax as Twitter hashtags or programming-language variables, which (at least at the time, in Twitter's case) don't allow a digit in first position; I've always used "+y2017" in a case like that.
In the meantime, libhxl-python shouldn't be rejecting the whole thing as valid HXL because of that one error; instead, it should just leave that column untagged. I'll look into it.
We had a file with attributes like "#affected+injured+dineo+2017" - starting with a digit which are not recognized as valid tag. Due to this, the file is marked as not having hxl tags even if it had other valid tags&attributes.
Q: do we need to change the pattern to support attributes that starts with digit?
note: this tag "#affected+injured+dineo+y2017" is valid
The text was updated successfully, but these errors were encountered: