Re: Voice session at TPAC

Thanks very much, Dirk,

I am in two CGs on this topic but was unaware of this one - which I have
now joined.

I can't join the call today unfortunately but will be interested in the
outcome, which we will feed into the discussion at TPAC in a couple of
weeks' time.

Cheers

Phil

On 04/09/2019 16:40, Dirk Schnelle-Walka wrote:
> Hey there,
>
> in parallel I started some activity to continue/start with the standardization efforts. See also https://lists.w3.org/Archives/Public/public-voiceinteraction/2019Aug/0000.html
>
> We will have a first call this Thursday.
>
> Unfortuantely, I will not be able to attend TPAC but would be interested in the outcome.
>
> Dirk
>
>
>> Léonie Watson <lw@tetralogical.com> hat am 4. September 2019 um 11:45 geschrieben:
>>
>>
>> I don't mind at all, thanks for including me Phil.
>>
>> On 04/09/2019 10:44, Phil Archer wrote:
>>> Thanks Léonie,
>>>
>>> I hope you don't mind but I've added your name, as well as Mark
>>> Hakkinen's, to the list of panelists, as he has also expressed interest
>>> in the session. I'll do my best to have a clearer idea of a structure
>>> for the session but essentially I'd like to just test the water, see
>>> who's interested in what aspects and go from there. My interest is the
>>> eCommerce side of course but that's just one aspect of what could be a
>>> really dynamic work stream.
>>>
>>> Cheers
>>>
>>> Phil
>>>
>>> On 04/09/2019 10:26, Léonie Watson wrote:
>>>> Thanks Phil. I'm definitely interested in this breakout session, thank
>>>> you for proposing it.
>>>>
>>>> The area that the Voice Assistant (VA) Standardisation CG was created
>>>> for, was to look at standardising the way we develop VA skills/actions
>>>> etc. At present it's a duplication of the problem we experience with
>>>> Android/iOS development, it needs to be developed and tested twice over,
>>>> there are "code once publish twice" platforms and tools, but they tend
>>>> to produce more brittle end results, and most existing VA devices
>>>> (Amazon Echo, Google Home etc.) use propriatary non-standardised
>>>> technologies to construct their voice UI architecture under the hood (as
>>>> well as some W3C standards like SSML).
>>>>
>>>> I still believe this to be a conversation worth having, even though I
>>>> haven't had time or energy to get this CG into motion (mostly because
>>>> I'm spending most of my time developing said voice skills/actions etc.!).
>>>>
>>>> Léonie.
>>>>
>>>> On 03/09/2019 10:38, Phil Archer wrote:
>>>>> Dear all,
>>>>>
>>>>>      From the evidence before me it seems, sadly, that both of these CGs are
>>>>> inert. If there is an active conversation going on elsewhere, please let
>>>>> me know. A recent Twitter exchange with Azizur Rahman at the BBC
>>>>> suggests there might be [1].
>>>>>
>>>>> In an effort to move things along a little... if you're going to TPAC
>>>>> this year, I hope you'll join me for a breakout session on the Wednesday
>>>>> to talk voice interaction/voice assistants. I've written a basic
>>>>> proposal for such a session in the unconference but would warmly welcome:
>>>>>
>>>>> - more specific topics within the general area of 'voice';
>>>>> - additional names on the proposal.
>>>>>
>>>>> Please see and, as appropriate, edit the wiki at
>>>>> https://www.w3.org/wiki/TPAC/2019/SessionIdeas#Voice_assistants_-_opportunities_for_standardization.3F
>>>>>
>>>>>
>>>>> [1] https://twitter.com/Azizur/status/1166335799165640704
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Phil Archer
>>>>> Director, Web Solutions, GS1
>>>>> https://www.gs1.org
>>>>>
>>>>> Register now for the GS1 Industry & Standards event
>>>>> Lisbon, 9-13 September https://standards-event-lisbon.gs1.org/
>>>>>
>>>>> https://philarcher.org
>>>>> +44 (0)7887 767755
>>>>> @philarcher1
>>>>> Skype: philarcher
>>>>> A word on abbreviations I sometimes use in email:
>>>>> https://philarcher.org/diary/2019/emailabbreviations/
>>>>>
>>>>> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
>>>>> If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
>>>>> GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
>>>>> GS1 may monitor communications.
>>>>> Third party rights acknowledged.
>>>>> (c) 2016.
>>>>>
>>>>>
>>>>
>>>
>>> --
>>> Phil Archer
>>> Director, Web Solutions, GS1
>>> https://www.gs1.org
>>>
>>> Register now for the GS1 Industry & Standards event
>>> Lisbon, 9-13 September https://standards-event-lisbon.gs1.org/
>>>
>>> https://philarcher.org
>>> +44 (0)7887 767755
>>> @philarcher1
>>> Skype: philarcher
>>> A word on abbreviations I sometimes use in email:
>>> https://philarcher.org/diary/2019/emailabbreviations/
>>>
>>> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
>>> If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
>>> GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
>>> GS1 may monitor communications.
>>> Third party rights acknowledged.
>>> (c) 2016.
>>>
>>
>> --
>> Director @TetraLogical TetraLogical.com
>>
>
>

--
Phil Archer
Director, Web Solutions, GS1
https://www.gs1.org

Register now for the GS1 Industry & Standards event
Lisbon, 9-13 September https://standards-event-lisbon.gs1.org/

https://philarcher.org
+44 (0)7887 767755
@philarcher1
Skype: philarcher
A word on abbreviations I sometimes use in email:
https://philarcher.org/diary/2019/emailabbreviations/

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). 
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. 
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. 
GS1 may monitor communications. 
Third party rights acknowledged. 
(c) 2016.

Received on Thursday, 5 September 2019 09:37:21 UTC