Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Very nice to meet you all my first year PhD student my Supervisor is ???  in the University of British Columbia and my research interest is in information governance empowered by blockchain, especially the healthcare sector so I think I got introduced to this meeting by Dr Vickie.   Actually i'm very new so I need to swim and follow some talk and I try to learn more about Trust Over IP because of this framework is actually. I come from Vietnam I just came to Canada, four years ago, so actually the whole area is fascinating to me, but everything is very new including healthcare information governance.

P A Subrahmanyam

I've been participating sporadically but reasonably often in the last several months. What I was looking for is essentially exposure or knowledge and as a reminder of sort of the different kinds of applications- commercial applications to know generally people working and around the topics we're discussing here right so so this I thought was a very good working group from that perspective and that's what excited me about it. Right,   It was educational in the sense of you know who are trying to apply this technology.  As opposed to the sort of a single minded dedication to the technology, which a number of people doing as well.  Help the YOMA task force in the early days and was in ISWG at times.

Karen Hand

I always find that you know these meetings with trust over IP is at the high point of the day and very hectic schedule soIt always feels good to feel connected to a community, so I would say that one strong point for Trust Over IP is that sense of community I think is very important.   So i've been involved over a year now, I came in because I participated in Ecosystem Foundry Working Group when Karl was chairing.  At that time and just really, really enjoyed the discussion and the people and the activities which led me into other areas of Trust Over IP.

So that's what brought me in.   I've been interested in probably everything, but I can only do so much.  So it's having to pick and choose what you can participate in and sometimes that goes up and down.  So I think that's important for members to understand that sometimes you can do it, and sometimes you can't, but it doesn't mean that you know you shouldn't still engage in whatever you can, even if it's just touching into a task force meeting or looking at a presentation that might be of interest to you.

I find that the Ecosystem Foundry Working Group is the touch point, or like as Karl would say "the service provider to all other layers."  I know that Trust over IP is new I see some wonderful evolution of the different Task Force and groups, for example, the Communications Committee that's now up and running and seem to have gotten their feet under them.

So it's more of how do we determine (and I think it's going to be really important the role) how do we utilize this group, as the touch point for all other activities?  How do we collaborate and communicate what's going on in ecosystems? 

A point was made earlier when I was saying "ecosystems is important because, for those who are technology minded it really brings the context to all the other work" So it's so key in that way for anybody who wants to or is working in creating an ecosystem.  How to reach out to the different resources or understand even what the ecosystem is?  So this this working group is crucial.  It's just crucial to everything that's going on all across Trust Over IP.

So I think one of the important roles of the income leader, will be to decide and look at what is the mandate and what needs to be accomplished for Trust Over IP to be more communicative and collaborative?  How do we get that going?   I think that will be really important!   

And one of the challenges that Karl and I talked about, and I think that we still need to talk about is, how to encourage the startups and the smaller groups, including my own work that I am hesitant to bring into the Community because you're always afraid, with good reasons.  I've had this happen, when of what you're doing being taken over or run with it in a different direction or by someone who has more resources.  So how do we get over that?  How do we create more of that kind of collaboration?  Maybe it's in more private groups, I don't even know if that can that can happen.

So that's what I see is the challenges right now. 

Personally speaking about the White Paper Task Forces.  What will be the mandate of that task force?  Given now that the Communications Committee is now running and taking over a lot of that really big work that needs to be done.  Doing really good work that needs to be done concerning, public publications, and communications such as podcasts, media, and so forth.  So that would be my my two cents.

Judith Fleenor stated that Communications Committee is not taking over White Papers.

Judith Fleenor recapped two touch points she heard from Karen.

  1. That the EFWG is the Glue that links the other working groups together.  The touch point for how to engage with the other working groups for both new people and ecosystems. The touch point that somebody and ecosystem comes to and then like, how do you engage with the other working groups. Keeping the other working groups aware of the business touch points and that applications.  Keeping in the forefront that complete ecosystems are about business process and trust relationships and not just about the technology.

Karen Hand

I would add that EFWG also serves as that translation between a business requirements and the business needs and the technology that would enable it because, well, I always say technology is a tool it's not the objective. So the ecosystem foundry working group helps work on the business objectives and requirements and then translating those business requirements into the technology that can that can serve those those objects of the business.

Judith FleenorAnd I think that's a really important role and kind of one of the directions, I would love to see the ecosystem foundry working group go  As Kimberly Linson also said...to perhaps create some of the artifacts of "how you set up an ecosystem" and what are the things that you need to be thinking about.  Linking those to the artifacts that are being created, and the other working groups.  This is the direction we started to go with PDCSi - having all of the working group chairs talk to that new ecosystem early on in the process.  So EFWG is that this is kind of the entry point for new people coming into Trust Over IP and creates the glue and the understanding of what Trust Over IP is and how they can get involved.  That's partly because of what P A Subrahmanyam said, which was there are so many interesting things that the presentations and things that that Karl put together that let you see kind of how an ecosystem sets up and what are the business processes needed in various ecosystems.

Eric Drury

The EFWG is probably the best, most logical place for me, but I do lurk on a lot of the technology calls, just so I can familiarize myself with the terminology and the concepts and all that kind of stuff.

Judith Fleenor it is alway ok to just Lurk and Learn during ToIP meetings.

Eric Drury I'm interested in the ecosystem foundry in the working group because, as you know, others have said, this is sort of the the the outward facing Working Group.  That takes information and goes off and and uses it.  I take that information to talk to business partners for use cases and things like that.  So I'm very interested whenever we have different organizations or use cases come in, so that I can see the similarities to the challenges and the approaches and the commonalities to the with those use cases to what i'm working on and so I really do enjoy hearing from others, and I guess the one thing that I've learned building an ecosystem is a long process, building an entire ecosystem, you know, rather than just starting with a single component and sort of allowing that ecosystem, to develop organically you're putting in place the different components, so that the ecosystem can can exist. I'm not sure that you actually build an ecosystem rather perhaps you and enable it by putting these different components in place. And for me, the challenge has been trying to figure out which components to put in place first so that we can then turn around and say I look now everything's ready for us to say you know for the connections to happen. So i'm I i'm engaged,  depending on my availability and depending on my geography and I split time between Cambridge England and Bangkok Thailand.  In the early days I did work on that task force that Kimberly Linsonmentioned. but I think Kimberly mentioned that scope was huge and we perhaps didn't start with small enough steps, or start with you know bite sized pieces. I'm here i'm happy I enjoy the discussions and conversations and learning.





More To Be Added

Action Items -