-
Notifications
You must be signed in to change notification settings - Fork 1
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
search for more potential types? #5
Comments
The current list of types is curated from these sources: JSON
PostgreSQL:
HTML and CSS:
RED (https://red-lang.org):
XSD Schema should be in here as well, it has a 'duration' type, which probably should replace the interval type. But I want to keep the base set of types limited. Similar to how HTML originally had only 20-30 elements. The idea is that it should be easy to write a complete parser/generator for JSONTag. The attributes are meant to add extensibility to the language, without creating incompatible parsers. As mentioned in #4 I think that points/shapes is potentially useful enough to add in the base set. PostgreSQL has these:
And finally I might want to add a specific type for errors ('error') as that is a vital part of many API's. |
In line with the email and phone type, an address type sounds reasonable as well. There can be no strict parsing rules for an address type though, since addresses come in so many varieties. Not just postal addresses, but IP addresses should be supported as well. So the tag should probably be defined as an opaque string. You can add an extra class attribute to distinguish between different kind of addresses. Will this add enough utility to jsontag though? You can also accomplish this by using
|
Protocol Buffers also have an extended set of supported types: |
Dive into the rabbit hole at https://en.wikipedia.org/wiki/Physical_quantity
The text was updated successfully, but these errors were encountered: