-
The SDK should recognize and properly handle 429 responses. The responses include headers which tell how long to wait until the next request. That's pretty easy to handle.
-
Provide a way to create an org.gedcomx.common.URI from a java.net.URI. Otherwise I'm writing this nonsense:
```
org.gedcomx.common.URI uri = new org.gedcomx.common.URI(ark.getURI().toString());
```
-
The example for the EvidenceReference Data Type (https://github.com/FamilySearch/gedcomx/blob/master/specifications/json-format-specification.md#37-the-evidencereference-data-type) has an index named …
-
Today, the gedcomx-php library supports PHP 5.3. This restricts us from using an older version of Guzzle (guzzle3). I'd like to bump PHP version support to >=5.4.
The primary customer who requested 5…
-
This may be a sore subject, but I'm wondering if the spec is now mature enough to redevelop RDF as a serialization option. I'm new, but I heard it was in the conceptual model before, and that didn't g…
-
The client should throw exceptions on the following HTTP responses:
- 401 - Unauthorized
- 403 - Forbidden
- 404 - Not found
- 405 - Method not allowed
- 406 - Not Acceptable
- 409 - Conflict
- 410 - …
-
See http://familysearch.github.io/gedcomx-php/docs/class-Gedcomx.Extensions.FamilySearch.Rs.Client.FamilySearchPlaceState.html
-
The RS clients should allow you to configure an agent string. This should work according to the HTTP 1.1 spec: http://tools.ietf.org/html/rfc7231#section-5.5.3
If nothing is set, it should set an age…
-
This library should have a Client that can be instantiated with all of the configuration options needed to authenticate and begin utilizing the API. The Client should provide interface into making req…
-
Why does gedcomx-rs specify [extension elements](https://github.com/FamilySearch/gedcomx-rs/blob/master/specifications/rs-specification.md#3-property-extensions)? All of the extension elements appear …