Re: Interesting case about profiles of profiles

OK now I understand the question, and +1 to Makx. In general the documentation aims at being as self-explanatory as much as possible. Though it's hard (and dangerous) to seek to copy everything, and some details may be left for readers to access elsewhere.
And of course for machine-readable expressions it's perhaps not the best way. But here it depends very much on the technology that is used. Fully modular machine-expressions are not that common.

Antoine

On 23/10/2018 15:24, Makx Dekkers wrote:
> The profiles that I have seen are complete documents, so they copy constraints from the inherited profiles, rather than only referring to those base profiles. That way implementers have everything in one place. That makes sense from a documentation point of view. Not sure if this would also be the best way for machine-readable expressions.
> 
> Makx
> 
> -----Original Message-----
> From: Karen Coyle <kcoyle@kcoyle.net>
> Sent: 23 October 2018 14:16
> To: public-dxwg-wg@w3.org
> Subject: Re: Interesting case about profiles of profiles
> 
> I think the flip side of this question is: are the profiles flat, using the DCAT-APs as an example? And if flat, are any operations expected to refer to the base profiles, or is each profile considered complete as it is?
> 
> kc
> 
> On 10/23/18 2:06 PM, Rob Atkinson wrote:
>> They have profiles of profiles.....
>>
>> do they have a way of generating a view of a profile with all the
>> inherited constraints - or is the use case for the client to walk the
>> hierarchy to find all the inherited profiles?
>>
>> On Tue, 23 Oct 2018 at 21:08, Antoine Isaac <aisaac@few.vu.nl> wrote:
>>
>>> Hi Rob,
>>>
>>> I'm afraid I don't understand your question.
>>>
>>> Antoine
>>>
>>> On 18/10/2018 12:56, Rob Atkinson wrote:
>>>>
>>>> Thanks Antoine - it doesnt surprise me a lot :-)   Did you find out if
>>> they had a mechanism to coalesce profiles (flatten out the hierarchy)
>>> to make them easier to use?
>>>>
>>>> Rob
>>>>
>>>> On Thu, 18 Oct 2018 at 21:25, Antoine Isaac <aisaac@few.vu.nl <mailto:
>>> aisaac@few.vu.nl>> wrote:
>>>>
>>>>      Hi everyone,
>>>>
>>>>      I'm in a workshop on semantic interoperability [1]. And there's
>>>> some
>>> interesting stuff on profiling, notably a presentation from Michiel
>>> De Keyzer working on public service registries.
>>>>      The vocabulary they use, CPSV [2] is an application profile of
>>> another vocabulary, CPSV [3]. And that application profile is in turn
>>> specialized into many profiles, either local or specific to a sector.
>>>>
>>>>      The interesting point it that these 'profiles of the profile'
>>>> are
>>> more numerous than the profiles of the base vocabulary. In a way, the
>>> original vocabulary lives rather through the first profile than on its own.
>>>>
>>>>      It doesn't change our requirement for allowing profiling on
>>>> several
>>> levels, but I though it enlightening to see that it can be confirmed
>>> to such extreme point...
>>>>
>>>>      Best,
>>>>
>>>>      Antoine
>>>>
>>>>      [1]
>>> https://ec.europa.eu/cefdigital/wiki/display/ETCOMMUNITY/Semantic+Int
>>> eroperability+for+Multilingual+DSIs
>>>>      [2]
>>> https://joinup.ec.europa.eu/release/core-public-service-vocabulary-ap
>>> plication-profile/22
>>>>      [2]
>>> https://joinup.ec.europa.eu/solution/core-public-service-vocabulary
>>>>
>>>
>>>
>>
> 
> --
> Karen Coyle
> kcoyle@kcoyle.net http://kcoyle.net
> m: 1-510-435-8234 (Signal)
> skype: kcoylenet/+1-510-984-3600
> 
> 
>

Received on Tuesday, 23 October 2018 13:36:41 UTC