Re: Introduction Voxtok and proposal for multiroom audio use-case addition to the draft spec

Hi JC.

I think it is a good idea to use a wiki and develop use cases there.
Requirements for each use case would additionally make it easier to see if
they are covered by the proposed solutions or not.

I've requested a wiki for the group (sysreq@w3.org). Once we get it, I
guess we could copy relevant structure from tv control API CG, and start
creating use cases (migrate from the spec?)

Ingar

2016-07-08 14:58 GMT+02:00 JC <jicheu@yahoo.fr>:

> Hi Ingar
>
> Thanks for your shared interest :) !
>
> In the past (TV Control API CG) what we did is collecting use cases in a
> separate wiki section [1], to keep the spec clean. From that we had derived
> the "holes" in other specs to determine the scope of work to do [2] and
> [3]. I was at the origin of the project but had to leave it in the middle
> of the river for business reasons, but Francois, who also was part of it,
> can comment and add informations on this.
>
>
> -- JC
> [1] Main Page/Technical Use Cases - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Use_Cases>
>
>
>
>
>
>
> Main Page/Technical Use Cases - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Use_Cases>
> Main Page/Technical Use Cases From TV Control API Community Group < Main
> Page Jump to: navigation, search Technical Use Cases of TV Control API
> Contributor: Bin Hu, AT&T
> Afficher sur www.w3.org
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Use_Cases>
> Aperçu par Yahoo
>
>
> [2] Main Page/Requirements Mapping - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping>
> [3] Main Page/Technical Requirement - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement>
>
>
>
>
>
>
> Main Page/Technical Requirement - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement>
> Contents 1 TV Control API Technical Requirements 1.1 General Tuner
> Requirements 1.2 General Channel Requirements 1.3 Tuner Channel Scan
> Requirements 1.4 General Program Requirements
> Afficher sur www.w3.org
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement>
> Aperçu par Yahoo
>
>
>
>
>
>
>
>
> Main Page/Requirements Mapping - TV Control API Community Group
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping>
> Technical Requirement Draft TV Control API Mozilla TV Manager API webinos
> TV Control API OIPF DAE v2.3 LG Connect SDK Samsung Web API GENIVI IVI
> Radio General Tuner Requirements tuner (summary)
> Afficher sur www.w3.org
> <https://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping>
> Aperçu par Yahoo
>
>
>
>
> Le Vendredi 8 juillet 2016 12h29, Ingar Mæhlum Arntzen <
> ingar.arntzen@gmail.com> a écrit :
>
>
> Dear Jean-Charles
>
> A warm welcome to the group for Voxtok and yourself !
>
> You are quite right, music is inherently both multi-device (multiple
> instruments) and timing sensitive, so it is indeed a very important
> application domain. Furthermore, shared timing offers interoperability
> across application domains, so there should also be new opportunities where
> musical experiences could be extended with timed visual, interactive and
> social elements, in a distributed setting.
>
> You are also right that we are currently a bit thin on this. This project
> was initiated through the Web and TV Interest Group, and for that reason we
> are a bit heavy on use cases related to video streaming and broadcasting.
> In any case, your suggested use cases would be most relevant and a welcome
> contribution.
>
> Currently, we only have one music related use case in the timing object
> spec [1]. We have also had conversations with people from the Web Audio
> community, but that has not been documented as a use case yet.
>
> Regarding how and where to develop new use cases, I'm not entirely sure
> which is the best way to go. We could keep adding use cases to the spec, or
> we could start collecting use cases on the group web pages or in a wiki?
>
> How would you like to approach this Jean-Charles?
>
> Francois, do you have a recommendation here?
>
> Best regards,
>
> Ingar Arntzen
>
>
> [1]
> http://webtiming.github.io/timingobject/#distributed-music-production-and-playback
>
>
>
>
> 2016-07-08 11:29 GMT+02:00 JC <jicheu@yahoo.fr>:
>
> Hi,
>
> As this is my first message in the group, please allow me to introduce
> myself: I'm the CTO and co-founder of Voxtok, a french company developing
> an audio system device allowing highend audio and a unified music
> experience on every device, including a device-less version for TV and STB.
> We strongly (around 105%) rely on web technologies for this ;-) In the
> past I had the chance to represent a member of the W3C including in the
> advisory board and am well aware of how things work here (ahem)
>
> I'd like to jump in into this fascinating proposal which is really in line
> with what we are willing to achieve in the most open possible way.
>
> I gave a quick look to the archives but couldn't find a discussion around
> adding a specific use case for music. If this has been done previously I
> sincerly apologize. Otherwise, I'd like to propose to contribute a new use
> case describing two scenario:
>
> - locally, many device play the same music, synchronously (what the
> industry calls "party mode")
> - remotely, you "join" a party and are allowed to listen to the same music
> listened somewhere else, by someone else. This as a social impact such as :
> "This is what I'm listening to right now, care to listen?"
>
> Before jumping to a more detailed proposal I'd like to get some feeback
> from the group,
>
>
> Again, thanks for the awesome contribution!
>
> Best regards,
>
> -- JC
>
> Jean-Charles Verdié
> CTO and co-founder,
> Voxtok
>
>
>
>
>