- From: Dirk Schnelle-Walka <dirk@switch-consulting.de>
- Date: Mon, 18 Nov 2024 16:52:24 +0100
- To: public-voiceinteraction@w3.org
- Message-ID: <4dc4399d-92b7-4962-a6f9-2f819d1d9f2e@switch-consulting.de>
Thank you Debbie, this could be one of the things that we may link to in our architecture draft. Currently, I find it a bit limited. At a first glance, I see * I am missing a clear identifier * supportedLayers and others seem to be restricted to written or spoken language, only * Only vague and not standardized means to describe the capabilities * serviceEndpoint is mandatory but there might be different means to access than by a URL, e.g. direct service call * No mentioning about authentication Dirk On 06/11/2024 19:17, Deborah Dahl wrote: > I put a link to more information about the Open Voice Assistant Manifest specification in the minutes today, but it didn't actually > have much information. Here's the actual specification. > https://github.com/open-voice-interoperability/docs/blob/main/specifications/AssistantManifest/0.9.0/AssistantManifestSpec.md > > The purpose of this specification is to provide a structured way for an assistant like an IPA to describe itself and its > capabilities as part of the process of discovering assistants that could handle specific topics. > >
Received on Monday, 18 November 2024 15:52:30 UTC