Sarven Capadisli

`getContentType` shouldn't remove `parameter`. If the intention is to get only the type/subtype, then another function name may be more clear.

@kjetilk "Only text/turtle is supported for RDF" wouldn't be accurate either because as it stands, NSS's rejection of the request may be due to the fact that the media-type value...

No issues with either one of those. They will create/replace resource given representation depending on request semantics. If /foo.txt exists, /foo.txt/ should not, and vice-versa. Redirect is optional.

Hmm, not exactly sure what you are after.. but there is no limit on how many or what representations can potentially be made available for a resource. Just one per...

>/foo.txt exists > POST /foo.txt creates a new file with a different location POST is an append operation, so server should append to the existing resource. POST to a (non-container)...

Servers are not required to "store" different representations or have URLs for them different than the resource URL. Server just needs to respond with a representation when a resource is...

Robustness applies. Two general approaches that are equally useful. Assuming that discovery always starts from a WebID: a. LDN based. Discover a WebID's inbox... b. Type registry based. Discover an...

Allowing A to be created at A but then allowing B to be updated so that A is effectively updated seems very strange.

>The Solid Protocol does not describe the requirements for the HTTP server hosting a WebID document. [1] The Solid Protocol does describe a WebID document served from a Solid server,...

As per WebID 1.0 ED, a WebID document is an RDF document. Representation in Turtle being the minimum requirement for interop whilst standard content negotiation takes place. The Solid Protocol...