search

w3c / voiceinteraction

publications of the W3C Voice Interaction Community Group
https://www.w3.org/community/voiceinteraction/
Other
15 stars 5 forks source link

problem statement #3

Closed dadahl closed 1 year ago

dadahl commented 3 years ago

from Jim Larson's email: https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0002.html I find this confusing.Is it hardware transparency, interoperability, or extensibility?

Include principles used to decide how partition the architecture into boxes, such as separation of concerns, each box does a single activity, etc.

dadahl commented 3 years ago

discussion from March 10 call https://www.w3.org/2021/03/10-voiceinteraction-minutes.html

jim: what is the problem?

debbie: I think it's interoperability

jim: I think that's the main purpose … describe principles about how the partition was arrived at … general software principles could be referenced … there is a nice hierarchical partitioning

debbie: we were using a traditional partitioning for conversational systems

jim: this should be included in the document debbie: agree

schnelle commented 3 years ago

@schnelle to add SW principle @dadahl to add problem statement

schnelle commented 3 years ago

added SOLID principle to section 3. architecture

schnelle commented 3 years ago

@schnelle to better match the SOLID principle explanation to the document

schnelle commented 3 years ago

Detailed the solid principle for this document

schnelle commented 3 years ago

Open point: @dadahl to add problem statement

schnelle commented 1 year ago

@dadahl I think that this issue is addressed by adding the SOLID principle. I suggest to close it if non objects.