Meeting minutes
issues for OVON Assistant Manifest
• 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
debbie: should add issue for the first one
dirk: only for voice or written language
… what if other assistants could create images
… or something else
dirk will add considerations to the Assistant Manifest issues
debbie: should make sure the list of layers is open
debbie: maybe input and output need to be separated
that should be added as an issue
dirk: key phrases may require a defined vocabulary.
debbie: key phrases were supposed to accommodate a stupid agent
debbie: for the description, we thought that the agent would have to be able to understand natural language
… we were thinking that the Discovery agent would already have indexed the universe of assistants
dirk: does that mean that every query has to already have been evaluated
debbie: indexing process would identify domains
debbie: the key phrases and descriptions would identify domain
dirk: will put this as an issue
dirk: service endpoint is mandatory, but does it always need to be a url, especially if everything is internal
dirk: what about authentication?
… also not all capabilities are on demand
dirk: like you can only create so many images
… depending on the authenticated user you could have a different manifest
debbie: I don't think web search engines use keywords to identify web pages very much anymore because of abuse and misleading key phrases