W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > July 2018

Re: Definition of 'a profile'

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Tue, 10 Jul 2018 20:44:15 +0200
To: <public-dxwg-wg@w3.org>
Message-ID: <f178f432-a548-e3b4-75d1-ef6081f12ac6@few.vu.nl>

I'm actually not against re-discussing the definition at some point, but I would suggest to do it later, once we have progressed on a document in which this definition will be. We've not made any tangible progress since February that would hint that we're in a position to re-discuss what's been agreed earlier. We've had such discussion for weeks already, not long ago. The group has then voted for a definition that includes the first sentence that Phil includes, word by word.
https://www.w3.org/2017/dxwg/wiki/ProfileContext#Draft_common_definition_for_.22profile.22

The consensus in the last call is that Phil's suggestion to add a bit about interoperability was desirable. We didn't agree on removing the definition we had already agreed on - and I think Phil's suggestion respects this.

If we want to reflect the full scope of our agreement in the past and add Phil's proposal, then the definition could become:
[
A profile is a named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. Such constraints should ensure that software systems that implement the profile are directly interoperable.
]
But again this is not removing the previous wording.

Antoine

On 10/07/18 17:02, Karen Coyle wrote:
> Don't keep us in suspense, Ruben! ;-) What do you think is needed to
> narrow the definition?
> 
> kc
> 
> On 7/10/18 5:06 AM, Ruben Verborgh wrote:
>>> This discussion leads to the following definition of a profile, also known as an "application profile" or "metadata application profile:
>>>
>>> A profile is a named set of constraints on one or more identified base specifications. Such constraints should ensure that software systems that implement the profile are directly interoperable.
>>
>> I've argued in the past that this is too broad.
>>
>> Under this definition, TypeScript is a profile, for instance.
>>
>> Best,
>>
>> Ruben
>>
> 
Received on Tuesday, 10 July 2018 18:44:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2019 13:45:00 UTC