-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Set index for SEMANTIC #1
Comments
A bit more details from our discussion:
and
|
I asked for advice from web developers. using "." character in JSON is not good practice, same for "-" , only "_" seems safe. |
what about "/" or "," , not good? "_" is ok by me. Are we already using that anywhere in our reserved Tony On Thu, Mar 14, 2013 at 5:59 PM, Fabrice Robinet
Tony Parisi [email protected] Read my book! WebGL, Up and Running |
I'm OK with "_", but why is "." a bad idea? It is inside a string literal; we should be able to do whatever we want. |
Yes, but is usually not recommended because they need to access a property like this obj['prop'] and can't do obj.prop in that case, which is what people tend to like more. To be honest I would really prefer "." I just don't want to upset JS purists here :). |
Gotcha. This is a non-issue for I'm OK with |
That is pushed. Closing. |
* Upgrade to json schema v4 syntax * More allOf changes
…ancing Rename KHR_mesh_instancing -> EXT_mesh_gpu_instancing
…justments factors in KHR PR feedback and fixes readme
Currently we have a couple of { semantic, set }.
Patrick suggested we could use a parsing convention like "semantic.set" so that we get a single property. Some implementation experiments and/or community feedback welcomed before changing this.
The text was updated successfully, but these errors were encountered: