Re: [External] : Objection to resolution to pause work on WoT Profile

That would be great, thanks Michael.

Let's keep the momentum going on WoT Profile so that it doesn't get
sidelined.

On Tue, 18 Oct 2022, 09:06 Michael Lagally, <michael.lagally@oracle.com>
wrote:

> Hi Ben,
>
> many thanks for flagging the problem and the suggested approach.
>
> To not cause any negative impact on the timely release of the Profile REC,
> I propose that we make the following a group resolution in the Architecture
> call tomorrow:
>
> "The main focus of the architecture TF for the next four weeks is to
> achieve CR status of the architecture spec,
> so the profile call slots are temporarily used for architecture.
> To ensure rapid progress of the Profile specification, the Profile work
> continues asynchronously
> on github / email, with on-demand discussion in the architecture calls, in
> case of any blocking issue."
>
> I hope this addresses your objection.
>
> Kind regards,
>
> Michael
>
> On 17. Oct 2022, at 17:14, Ben Francis <ben@krellian.com> wrote:
>
> Hi all,
>
> I note that in the last WoT main call a resolution
> <https://urldefense.com/v3/__https://www.w3.org/2022/10/13-wot-arch-minutes.html*t09__;Iw!!ACWV5N9M2RV99hQ!PVvF0LtTqr8yq5b_nT-KHVtsNWG3LPDF48M4fF4FRq7aa-2CuYlyi4itdLDu_qsXSPRXXUJJwoyPVFPw$>
> was proposed to pause work on the WoT Profile specification until WoT
> Architecture reaches CR status:
>
> temporarily pause the profile work until the CR has been done. After that
>> we use both call slots for profile.
>>
>
> In accordance with the WoT Working Group's decision policy
> <https://urldefense.com/v3/__https://www.w3.org/2020/01/wot-wg-charter.html*decisions__;Iw!!ACWV5N9M2RV99hQ!PVvF0LtTqr8yq5b_nT-KHVtsNWG3LPDF48M4fF4FRq7aa-2CuYlyi4itdLDu_qsXSPRXXUJJwpMFFoW5$>,
> I'd like to politely object to this resolution.
>
> To clarify, I don't have any problem with the current WoT Profile call
> slot being used for WoT Architecture discussions for the next four weeks as
> originally proposed (I'm actually unable to attend that call slot for the
> next four weeks anyway due to other commitments). But I would like to
> propose that members continue to collaborate asynchronously (using GitHub
> and email) on the remaining open pull requests (currently 10) and issues
> (currently 18) for Profile 1.0 during this time, in order to work towards a
> new Working Draft as per an earlier resolution
> <https://urldefense.com/v3/__https://www.w3.org/2022/10/12-wot-profile-minutes.html*t02__;Iw!!ACWV5N9M2RV99hQ!PVvF0LtTqr8yq5b_nT-KHVtsNWG3LPDF48M4fF4FRq7aa-2CuYlyi4itdLDu_qsXSPRXXUJJwlCtGOMI$>
> made on the WoT Profile call. If we want to transition the specification to
> REC status early in the next charter as proposed then I don't think we can
> afford to slow down and we need to get the specification into a stable
> implementable state before publicising a call for implementations.
>
> Proposed modified resolution:
> "Temporarily pause the WoT Profile calls for four weeks and use the slot
> for WoT Architecture discussions."
>
> Best regards
>
> Ben
>
> --
> Ben Francis
> Founder
> Krellian Ltd.
> <https://urldefense.com/v3/__https://krellian.com__;!!ACWV5N9M2RV99hQ!PVvF0LtTqr8yq5b_nT-KHVtsNWG3LPDF48M4fF4FRq7aa-2CuYlyi4itdLDu_qsXSPRXXUJJwj3psN9l$>
>
>
>
>
>