You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing familysearch/gedcom SDKs are generic which makes them hard to use. In order to better integrate, a JSON Schema is needed so that code can be auto-generated to match the models and create much more usable SDKs. Parsing the github markup or html would take just as much work as manually creating code models to match the format. http://json-schema.org/ is leading the way in this regard and is what should likely be used. If there was a JSON Schema available, custom SDKs could be easily generated which would make integration more simple.
The text was updated successfully, but these errors were encountered:
I agree that a JSON Schema would be helpful. If anybody would like to pick this issue up and submit a schema, I'd be happy to review it and add it to the project.
The existing familysearch/gedcom SDKs are generic which makes them hard to use. In order to better integrate, a JSON Schema is needed so that code can be auto-generated to match the models and create much more usable SDKs. Parsing the github markup or html would take just as much work as manually creating code models to match the format. http://json-schema.org/ is leading the way in this regard and is what should likely be used. If there was a JSON Schema available, custom SDKs could be easily generated which would make integration more simple.
The text was updated successfully, but these errors were encountered: