Re: [Vcon] CC gap analysis of draft-petrie-vcon

[Daniel Petrie <[e-mail]>]

 Jonathan and Andrew:I have addressed some of the missing meta-data, but there are a few items that I need a little help with.
Interaction Type: the vcon draft has the Dialog Object type and mimetype parameters (section 4.3.1 and 4.3.6).  This allows us to differentiate from text, audio and video interactions.  It does not neccesarily allow us to differentiate from text interactions such as email, SMS and web chat as they are all text.  It also does not let us differentiate from a video call or conference from agent screen captures which might both be video recordings.  Do we need this differentiation or is text, audio and video sufficient as differentiation of Interaction Types?
Interaction ID: It is not clear to me what the scope of an interaction is.  If an agent does a web chat and then a phone call, do they both have the same Interaction ID or are they two different interactions?  I am trying to determine if the interaction ID belongs to the Dialog Object or the whole vCon.
Skill: I am having difficulty what we label with Skill.  It seems to me that the whole conversation/Vcon may have a required skill and that each dialog in the conversation might have a required skill and it could be different for each dialog in one vCon.  At the same time a Party in the conversation may have a set of skills.  Should we be labeling each Dialog Object with a skill required and some parties with a list of available skills?
Campaign and Dialing List:  Are Campaign and Dialing List really two different parameters?  These strike me as potentially identifying the same thing.: the context/customer/product/script to/for which the call is placed or received.  Please help me understand how they re different.
Cheers,Dan

    On Thursday, February 29, 2024, 10:25:04 PM UTC, Dan Petrie <[e-mail]> wrote:  
 
 I have been going through https://www.ietf.org/archive/id/draft-rosenberg-vcon-cc-usecases-00.htmland working on gap analysis for https://datatracker.ietf.org/doc/draft-petrie-vcon/
in preparation for an update to the draft to cover what is missing.
For the most part I think that draft-petrie-vcon support the architecture, applications, concepts and topologies outlined in rosenberg-vcon-cc-usecases.  There are some gaps in draft-petrie-vcon for some of the meta-data defined in rosenberg-vcon-cc-usecases.  I have gone through the meta-data defined in cc-usecases and created a table outlining what is supported by the draft-petrie-vcon02 and what is not along with references to what is supported and a first pass suggestion on actions to add support of the missing meta-data.  I plan to update draft-petrie-vcon over the next few days.  During this time, I would love to have feed back on this.  Sorry, I know this is not a lot of time, but the draft deadline is March 4th.  So to get it in the next draft, I need your comments before then.
Here is the table of what I think is supported and what needs to be done to add support of the missing meta-data:https://github.com/dgpetrie/draft-petrie-vcon/blob/main/cc-usecases-gap.md

I also hope to see you all in Brisbane.
Cheers,Dan