[asgeo1]

Addresses issue from #36, so user can either PATCH or PUT objects in Weaviave class as required.

[andreibondarev]

@asgeo1 Would you please update the specs as well? Thank you!

[andreibondarev]

Thanks for this, and for raising #36! The update (PATCH) / replace (PUT) split for objects shipped in 0.9.0. For collections, Weaviate's API has no PATCH /schema/{className}, so #72 fixes update by merging the changes into the current definition and sending a full PUT instead. Closing as covered by those two.