Re: [Specifications] void:classPartition

Ah, Linked Data Fragments. ’void’ may be a good fit there. After all LDF is used exactly with coherent RDF datasets.

But not every API will be considered a dataset in that sense IMO. 

Not to mention that Hydra would be used to describe non-RDF APIs too, right? I woldnt want to describe RDF datasets to people who only want to describe rich HTTP interactions...

⁣-- 
Tomasz Pluskiewicz ​

On Jun 23, 2017, 01:12, at 01:12, elf Pavlik <notifications@github.com> wrote:
>> Excuse my severe lack of RDF knowledge, but what is
>void:classPartition? Its description makes me none the wiser and your
>example leaves me both dizzy and puzzled.
>
>https://www.w3.org/TR/void/#class-property-partitions
>
>> I'm not convinced either. Hardcore RDF people will immediately notice
>that this implies that /api and /api/events/ are void:Dataset. Is that
>your intention? I think they aren't because the notion of dataset is
>somewhat disconnected from an API (set of resources)
>
>API provides an interface to a dataset, and I see no problem with
>considering a collection a subset aft that dataset (so also a dataset)
>
>Maybe @RubenVerborgh could chime in since he uses `void` in Linked Data
>Fragments specs.
>
>
>
>-- 
>You are receiving this because you commented.
>Reply to this email directly or view it on GitHub:
>https://github.com/HydraCG/Specifications/issues/126#issuecomment-310527247


-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/126#issuecomment-310623667 using your GitHub account

Received on Friday, 23 June 2017 09:50:26 UTC