Meeting minutes
GitHub issues
dirk: discovery and interaction
debbie: interaction format is in interfaces
debbie: could look at OVON Assistant Manifest
… but actual discovery could be outside the standard
… could be like Google or search engines
dirk: could add a section in the Provider Selection Service
debbie: registry could be like DNS
dirk: publish-subscribe service
… question i "please link me with something that can do bank account management"
… add a sentence to the provider registry component to talk about the need for discovery
debbie: we could talk about the OVON Assistant Manifest
https://
debbie: let's talk about the Assistant Manifest next time
issue 62
debbie: I just added a paragraph in the introduction about LLMs
debbie: should we say that we have two versions of the architecture, one for traditional and one for LLMs
… actually we have two variations of the architecture
debbie: delete "this" sentence and then change the previous sentence to refer to different variations.
dirk: nothing else should be added
added new wording for issue 62
debbie: will add a new use case (Section 2.1.4)
debbie: I'll think about that but I don't want it to be too much like the use case in 2.1.3
dirk: taxonomy of private data types.
issue 60?
debbie: how should we proceed with issue 60?
gerard: some data really needs to be encrypted
debbie: where to put this discussion? Could be a new document
dirk: should receive its own section if it's in the architecture document
dirk: other researchers don't make these distinctions.
debbie: should find a place in the architecture document
… add privacy and security of data after error handling
gerard: can add a section on privacy of data, new section 4
dirk: issue 59, this is a special case of issue 60
… issue 59 could be an example of the need for privacy
dirk: could be too specific for our document
gerard: could write something about using homomorphic encryption in the cloud
dirk: we could just close this issue as being too specific for this document
issue 58
dirk: personal just mean that it could learn about the user
… could add a clarification that we're using personal in that sense
debbie: but doesn't mean "personal" in the sense that it has your data