- From: Annette Greiner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Feb 2019 06:55:56 +0000
- To: public-dxwg-wg@w3.org
Okay, so, I've got something to look at over at https://agreiner.github.io/dxwg/dcat/. This is mocking up how I imagine it would look if we were to make use of the distinction between an API and a web application to define subclasses of data services. I've also uploaded an SVG for the overview UML diagram, so future iterations shouldn't need to be redrawn from scratch. I'm still debating in my mind whether we might want to add a property architecturalStyle that takes literal text. I've been unable to find any attempts to standardize such a thing. Yet, it's probably the first question any programmer would ask when deciding whether they want to dig into a given API (after "Is it an API or just a web site"). One can use conformsTo to indicate a standard, but there is no real standard for the most common type of API on the web (REST). If anyone knows of a reasonable codification of architectural styles, that would be great to check out. -- GitHub Notification of comment by agreiner Please view or discuss this issue at https://github.com/w3c/dxwg/issues/432#issuecomment-459626118 using your GitHub account
Received on Friday, 1 February 2019 06:55:58 UTC