What limits are placed on names in $defs
and data type names?
#185
-
Hi all, This is a bit of a silly question, but a cursory read of the draft RFC for JSONSchema and various documentation items has thus far not answered it for me. What names are valid in the name of a My intended use case is to basically be able to describe a SQL database tables through JSONSchema documents. The goal being a kind-of HTTP-based ORM, which coupled with a suitably specified ReST API specification and using JSONSchema-based form generators for the front-end, would pretty much give you a pretty powerful declarative ORM web-application framework without having to write much in the way of SQL or JavaScript/HTML code. Specifically I'd like to be able to encode both "generic" types (e.g. Are there any gotchas I need to be aware of? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Interesting! I'm doing something similar (I think) with Apache Tinkerpop's Gremlin query language for graph databases. You might want to bring this discussion to the Slack discussion.
I'm not sure what you mean by "name used in a field data type"? The |
Beta Was this translation helpful? Give feedback.
Interesting! I'm doing something similar (I think) with Apache Tinkerpop's Gremlin query language for graph databases.
You might want to bring this discussion to the Slack discussion.
$defs
names are just JSON object names and can be anything that is syntactically legal in that sense. Of course, some names will require URI-encoding to be used in JSON Pointer fragments, but if you're using a proper implementation of JSON Pointer and constructing URIs with a proper URI library, that won't be an issue.I'm not sure what you mean by "name used in a field data type"? The
type
keyword is not extensible.