- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 May 2019 19:31:36 +0000
- To: public-hydra-logs@w3.org
For me `SHOULD` in point 1 is a bit to strong - I'd go with `MAY`. Why? The schema.org is has some issues. There is an RDF serialization available directly from schema.org domain, but it does define ranges with it's own terms (schema:rangeIncludes) and not with rdfs:range. Having `SHOULD` there may end up with crafting custom ranges with may be actually wrong. As for WSDL - API Documentation is just a helper to give some hint for clients on the pre-computation stage. Spec mentions that client should always acknowledge responses in the runtime as these may not provide data exactly as the API documentation states. The API is supposed to provide hypermedia after all. In SOAP environment WSDL was the only option. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/192#issuecomment-491955278 using your GitHub account
Received on Monday, 13 May 2019 19:31:38 UTC