
14:06
If this is the first time you are joining the meeting of this WG and would like to introduce yourself - you can do so using voice or chat. Please use (name/affiliation/location) format

14:48
Sorry, juggling two meetings

18:30
https://github.com/trustoverip/deliverables/issues/4

20:40
I think you will need a Linux Foundation account.

21:08
How do I know if I have a Linux Foundation account?

21:40
@carly, did you sign up for TOIP? I think that creates the account

22:16
https://docs.google.com/presentation/d/19WEajAKEFftf98bDqLZ4G-igxa2mZg6AmbK8_M7YQBA/edit#slide=id.g8d7f9de172_5_1

22:27
You will have to use the same email that you provided while joining the Linux Foundation

22:54
Well, for what it's worth I just used my personal GitHub and got access..

22:59
hmmm

23:18
That St. Clair. He’s always going rogue…:-)

23:38
Will someone on the call be also able to edit the meeting page and scribe notes?

23:39
Wow, then it is open as mentioned by Dan

24:24
Maybe it is open, but we will always know who did what and what they did and can always go back…

25:48
I will scribe offline @Sankarshan and share/update later on - I hope that helps

26:02
Thank you Kalyan!

26:16
ACK. Thanks Kalyan.

26:23
I’m quite sure we’ll do some “storming” around the roadmap :-)

26:40
Moving from storming to norming requires strong leadership that can then back off once norming is achieved (and is almost invisible when performing is achieved).

26:52
Well said

30:03
We need to try and break the 80/20 rule...

30:37
…by which you mean, Jim?

31:27
Just the traditional challenge that 80% of commits are made by 20% of coders, in this case..

34:15
The Sovrin Governance Framework really only covers Layer 1 right now.

34:24
The new Sovrin Ecosystem Governance Framework will be for Layer 4.

34:37
Ya may want to consider the CONSUMABILITY of the WG work products. Meaning how does an Ecosystem or Utility pickup your templates and use them.

34:44
I’d want to also do a time check - we are halfway into the meeting. If we are going to pick and choose topics off the agenda - let’s do that to do justice to the audience participation today.

34:59
+1

35:09
+1 Dan

43:05
Dan, do you mean a spec to transfer info between layers?

44:28
As co-cahir of TSWG on we need to deliver Layer Interop Specs https://github.com/trustoverip/deliverables/blob/master/_process/work_products.md#layer-interoperability-specifications

45:26
@DanG, agreed. The primary focus of the TSWG is the space between layers to ensure interoperability. The primary focus of the GSWG is within each layer.

46:57
+1 Scott

47:32
Something like an API

47:41
Good analogy Drummond

48:47
“Battle of the Forms”

52:47
We are Input to Terms

53:10
There possibly would be an overlap between what GSWG brings out and Concepts group bring out and right one will probably make it to the books

56:12
We should assume that C&T will be required to minimally produce 4 glossaries (1 per WG).

59:54
What about a white paper that describes a prototype ecosystem from top to bottom presented in narrative story form?

01:00:08
Ooooh, I love that idea

01:00:15
Just a note, I mentioned in the TF call today this matches up with the 36 mo delivery on the ISO standard

01:00:20
+1 scott

01:00:25
I really feel we can get a template for Layer 1 pretty quickly.

01:00:45
@Scott, that sounds like a good deliverable for the Ecosystem Foundry WG that we and the TSWG could contribute to

01:00:46
Leverage outlines from Sovrin and BBU and you have a starter

01:01:32
@Dan, I agree that the template for Layer 1 should be first—and if we have enough people power, we could get it done by EOY

01:01:57
@Dan, good idea, and maybe leverage MyData, too. @Drummond, exactly.

01:02:22
+1 Drummond and I would go one step further .. we can offer tooling for generating web/pdf renderings of a template instance.

01:02:34
This is the page Scott is displaying: https://wiki.trustoverip.org/display/HOME/Classes+of+Verifiable+Credentials

01:03:56
LoA could be defined for any type of verifiable credential if it’s needed—but it’s highly contextual.

01:04:56
We need to use Scotts example content to make a point. How do we classify this Trust Assurance content. Is it in a template? Recommendation? Other?

01:05:22
IMO it is a Recommendation.

01:06:30
This is great work.

01:06:40
At current state it certainly reflects more as a recommendation but can transform into a template - one for each class

01:07:19
Another recommendation would be which class is best for a given type of credential.

01:10:06
It sets a good start

01:10:10
All good comments BUT we must strive for CONSUMABILITY of our workproducts. If ToIP is too complex it will be a hit against us.

01:10:32
Agree @Dan

01:13:30
How much diversity do you have in the room to engage with the governance. I see no women of color here. Very few women and my my read no folks from the global south.

01:13:32
Thanks everyone!

01:13:33
Great start