-
Notifications
You must be signed in to change notification settings - Fork 17
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
Advanced GeoPose JSON encoding not JSONic #69
Comments
Sadly, this is a known issue, where @3DXScape insisted on using strings instead of proper JSON schema. I believe it was in part to not have to cover that part in the current specification of the standard (allowing third parties to extend the system in a different, URL-based way), but it is making the implementation of the Advanced types of GeoPose very difficult. I would suggest that, instead of using arrays of strings for external systems, we modify the standard to include a proper JSON schema for the types of advanced positioning systems that we actually need to take into consideration. |
See also #70 about trying to make the more advanced capabilities simple extensions to the basic GeoPoses. |
(apologies in advance if this sounds too critical and for providing feedback at this very late stage, but I believe this is an important issue)
About the Advanced GeoPose JSON encoding (9.2.4), is there any particular reason why parameters are encoded within a string in a URL-like manner, rather than in the natural JSON way of using objects and arrays?
i.e., why:
instead of:
Similar question for the integrityCheck escaping double quotes and curlies in 9.2.7. Why:
instead of:
It necessitates separate parsing passes on the strings and unless there is a really good reason, it seems to defeat the purpose of a JSON encoding.
The text was updated successfully, but these errors were encountered: