Content-Type: message/external-body description insufficient for conformance tests

[kefo]

The description for Content-Type: message/external-body lacks the details to confidently write an API conformance test. Quoting 3.4.1:

Implementations MUST support Content-Type: message/external-body extensions for request bodies for HTTP PUT to LDP-NRs. This content-type requires a complete Content-Type header that includes the location of the external body, e.g Content-Type: message/external-body; access-type=URL; URL="http://www.example.com/file\", as defined in [RFC2017].

As written, the header is noted to be an example, "e.g. Content-Type:..."

Is access-type=URL the only supported type (assuming a restriction)? Is access-type=local-file supported? See rfc2046.

Resolving #40 is also needed.

[awoods]

@kefo : I believe this issue has been resolved with: #121
If you agree, would you please close this issue?

[awoods]

Resolved with #121