Re: Swagger JSON Docs & Linked Data

On 7/2/17 4:24 PM, james anderson wrote:
> good evening;
>
>> On 2017-07-02, at 21:48, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>
>> On 6/30/17 12:17 PM, Kingsley Idehen wrote:
>>> On 6/29/17 7:03 AM, Gray, Alasdair J G wrote:
>>>> Hi Martynas
>>>>
>>>> The Linked Data Templates look like a really interesting way of
>>>> getting a read/write data web. However, I’m unclear whether you
>>>> support data returned in non-RDF serialisations, e.g. CSV, or JSON.
>>>>
>>>> […]
>>>> It would be a huge limitation of the Linked Data Templates if they
>>>> did not support serialising to CSV, JSON, etc.
>>>>
>>>> […]
>>> Hi Alasdair,
>>>
>>> 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-economy-rest-linked-data-and-a-semantic-web-9d6839dae65a
>>> -- Swagger, the API Economy, REST, Linked Data, and a Semantic Web
>>>
>>> Kingsley
>>
>> Alasdair,
>>
>> I've located the JSON-based Swagger doc I inquired about. Once again,
>> this brings discovery to the fore i.e., adopting any combination of the
>> following to aid structured data discovery:
>> […]
> from my reading of martynas’ document, this misses the point which linked data templates (ldt) intends to make.

Hi James,

Can't you see that I deliberately changed he topic heading for this thread?

>
> wrt encoding, that is a protocol-level matter, for which http and content negotiation provide adequate support independent of the mechanisms proposed for ldt.
>
> wrt to discovery and api introspection, while any thing which facilitates manual comprehension is valuable, ldt concerns a means to drive the implementation from the specification, not specifically its comprehension.

My post is about accommodating either approach rather than demanding a
specific approach.
> a cross-over between swagger and the ldt specification language sounds like something interesting, but does not directly concern the ldt facilities themselves.

I made the mistake of not altering the topic heading when responding to
Alasdair in regards to the OpenPHACTs API he mentioned. 

>
> best regards, from berlin,
> ---
> james anderson | james@dydra.com | http://dydra.com
>
>
>
>
>
>
>

-- 
Regards,

Kingsley Idehen       
Founder & CEO 
OpenLink Software   (Home Page: http://www.openlinksw.com)

Weblogs (Blogs):
Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog: http://kidehen.blogspot.com
Medium Blog: https://medium.com/@kidehen

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
        : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this