-
Notifications
You must be signed in to change notification settings - Fork 160
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
Clarify handling of regex-based parsing #312
Comments
In some other places, we reference a grammar and productions within the grammar. Can we do that here? |
Unfortunately, you have to purchase ISO 8601 to get the full text, so if we referenced something in ISO, our document would become less accessible. From this openly available draft of ISO 8601-2 it seems that there is a grammar, but only for the extensions, not the main date/time format in ISO 8601-1. So we'd probably end up writing a grammar anyway. |
Ah, there's a grammar in https://www.ietf.org/rfc/rfc3339.txt appendix A. |
Yeah, we can cite RFC 3339 normatively here, rather than ISO 8601. |
Time zones are probably the hardest case here, since they have a couple of alternative syntaxes. |
We've got text like
That's not great. I don't know what the best solution is, though - perhaps creating actual JS RegExp objects? Thoughts welcome.
The text was updated successfully, but these errors were encountered: