Re: [dxwg] A profile must be packaged as a self-contained artefact

Sorry but this is just wrong. Dcat-ap imports dcat so ergo it is not flat.

I do agree that mechanisms to flatten are useful and implementations must
be allowed to choose these options. I think perhaps you need to develop a
specific use case around the provision of flattened packages (and there is
always a point at which you decide the client just needs to know something)
rather than trying to question the evidence for the existing practice of
defining profiles in hierarchies.

A client that "knows" dcat might be able to use dcat-ap as a flat
profile... but whatabout geodcat-ap or dcat-ap-it.

Nothing stopping dcat-ap-it being acaikable as a flattened graph containing
all the dcat and dcterms axioms. These are distributions of the profile
itself.. so would be great to have this Use Case articulated.


On Sat, 23 Jun 2018, 01:02 kcoyle <notifications@github.com> wrote:

> @rob-metalinkage <https://github.com/rob-metalinkage> All of the DCAT
> profiles are flat. If you are referring to profiles in some
> machine-actionable form, we don't currently have any in our examples so
> please add any that you know about to our list of resources on the home
> page. (Actually, the original BIBFRAME profiles were machine-actionable but
> 1) are not being used and 2) didn't include anything but vocabulary terms
> 3) are flat.)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/dxwg/issues/228#issuecomment-399472946>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AIR3YZINnmsjNwkPGOQdD02QJfFur8zYks5t_QcJgaJpZM4T2ZYK>
> .
>


-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/228#issuecomment-399717643 using your GitHub account

Received on Saturday, 23 June 2018 23:38:06 UTC