Geoff Rispin

Pull Request Ref: https://github.com/RESOStandards/transport/pull/137

Here is the link to the DD change proposal as well. https://reso.atlassian.net/wiki/spaces/DDGDF/pages/9525100546/Web+API+Add+Edit+with+Media

@bryanburgers The manipulation of the order of `Media` resource records should be handled by the existing OData Add/Edit part of the specification. It would be standard update of the `Order`...

RESO does not have a stated policy on how the value of `Media`.`Order` field should affect other records beyond the one that is updated. Most common case that I have...

To support media uploads, we would like to request a boolean field be added to the `Field` and `Model` resources to represent the `HasStream` attribute from the EDMX. This is...

We should add that attribute to keep the Model/Field/Lookup in sync with the EDMX.

On the certification side of this, We should exclude deprecated fields from certification process for off market listings to reduce the impact of large historical datasets to future DD version...

Completely agree. This just about how bring explicit about deprecation means within the testing rules of certification. We have not documented how deprecation would impact certification testing in detail yet....

There is currently a gap in the Webhook subscription proposal that i brought up previously. The Webhook proposal requires Oauth authentication for the subscription proposal does not provide a method...

This proposal has been simplified to just a single checksum (two text fields) based on the industry standard [W3C Sub-resource integrirty (SRI) ](https://w3c.github.io/webappsec-subresource-integrity/#the-integrity-attribute) model for file checksum behavour. We would...