Re: [Specifications] How to document forbidden dereferencability (#216)

>It doesn't matter if it's RDF.

To some degree it does. I think this may be one of the reasons IANA media type profile could be impossible to downgrade as it may not be machine-readable.

>the server MAY ignore the client's capabilities and use unsupported profiles
or omit operations which the client will not understand

I don't think it's good approach. If client doesn't understand something, it should ignore it.

>No, profiles exist regardless of what Hydra decides to do in this space

These are not profiles - these are extensions. I'd call profile something we could _ebrace_ in spec.

Anyway, lets get our discussion back to the topic - which solution and how could make it happen?

-- 
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-635608782 using your GitHub account

Received on Thursday, 28 May 2020 21:08:58 UTC