Hi. Martynas, do you think it would be difficult to implement a Binding for a Profile / Node mapping spec in my platform so, for example, I could embed LDT, SoLiD and others for publishing and consumption from / to any other integrated protocols / formats? Please read document below for reference. https://docs.google.com/document/d/1OqsVn6uo0cr6qruzWj9yRASrmvAIAf4HsHuLS2aRSy8/edit?usp=drivesdk Best. Hi Kingsely and all I agree with this: > Have you considered using OpenAPI (nee Swagger) to document your APIs? > Doing that would provide another point of intersection between "Web > Developers" and "Semantic Web Developers" . > > > [1] https://medium.com/openlink-software-blog/swagger-the-api-ec > onomy-rest-linked-data-and-a-semantic-web-9d6839dae65a -- Swagger, the > API Economy, REST, Linked Data, and a Semantic Web > > moreover I would guess that approaching to API design as a collaborative effort (even before providing the actual underling implementation) could be a way to deepen the discussion. The community could be interested in merging approaches and best practices, as Kingsley said, avoiding choices that could be problematic on one of the side (for example opaque URI,, and so on...). Given the current status of stadards, with LDP, LDF, it would be useful to underline in a practical manner the benifits of a "new" standard around resources. For example for some reason I imagine some similarities with the ideas behind the "old" Fresnel approach in some way (at least when reading/navigating a resource) here (am I completely wrong?), but maybe I didn't understand at all the context :-) Engaging people around playable wip examples could be a way to focus on the crucial parts. my
Received on Friday, 30 June 2017 17:15:36 UTC