
20:46
I don’t want to just discuss - it’s important that we can implement.

20:59
q is orie

21:25
q+

21:33
q is empty

21:38
q

21:44
q is Oliver

22:12
q is Oliver and Kyle

22:20
q+

22:27
Q is Kyle and Jonnycrunch

23:08
Q is Jonnycrunch

24:14
Q is Orie

24:25
We need to be able to interop - best practices is not sufficient.

25:21
q+

25:29
q is Orie and Dimiti

26:17
Q is Dimitri

26:47
q+

26:54
Q is Dimitri and Troy

27:22
Q is Troy

27:28
Q+

27:34
+1 for this rework & agree w/ Jonathan's trepedations

27:38
"... user data, including metadata and index data..."

27:39
I was just able to join until now

28:19
q is Daniel

28:24
The forcing only encrypted data and forcing indexing is something I'd object to if they're mandatory

28:53
q is empty

29:55
+1 to optional indexing.

29:57
Makes sense Daniel.

30:14
https://docs.google.com/document/d/1lYEWdDOm1iyCN9q_AkHE3bQ_SDjhwHDYWp73a73F4M8/edit#

34:33
q is empty

34:42
Oh boy, that's going to be a can of worms

34:58
Let's not fight about that yet

35:05
Haha!

36:00
q

36:08
q is oliver

36:14
Thanks!

36:17
q is George

36:26
no

36:35
q+

36:46
q-

36:57
q is empty

37:26
This is implementation concern

37:39
Please lets not discuss this….

37:44
+1 orie

37:48
Implementation concern

37:57
Don’t think it is worth getting sidetrack on now

38:19
Are you objecting to HTTP?

39:00
Agreeing to use HTTP and creating something that is entirely bound to exclusively HTTP is a different thing

39:13
Please don’t mention didcomm

39:19
Please don’t talk about how....

39:36
+1 Tobias commet

39:48
emtpy

40:47
Yes

40:56
q is Kyle

41:09
I didn’t see you opened my comment — yes, concern addressed

41:50
q is Kyle, Orie

41:57
Q is Orie

42:18
q is empty

43:03
yeah!

43:08
rofl

44:03
yes

44:35
sorry one second

44:43
mice is not working

44:52
Do you object?

45:02
just wanted to maybe mention quantuam resistance as a goal

45:29
No objection

45:35
q is Orie

45:40
q-

45:43
goal to support quantum resistance.

45:54
q is empty

46:46
Or if you feel like its already covered, feel free to let us dismiss it… I feel that its already covered by existing language..

49:45
its someone's highlight^^

51:36
Yes, things that exist already in other groups… are in scope...

51:45
Can it be work going on at Hyperledger?

51:54
Yes, I imagine so

52:30
DIDComm can happen over HTTP

52:38
^

53:08
…

53:12
No daniel

53:17
Such discussion is in scope.

53:45
We don’t need more language to address that concern...

54:12
Are you objecting?

54:30
q is Orie

54:50
t-10 min left

54:53
q is empty

56:14
come on... I want to be able to use SDS with physical package carrier services 😁

56:28
No Kyle. :)

56:44
under what mechanism?

56:47
q

56:49
Kantara?

56:54
q is Oliver

57:11
No objection

57:14
q

57:19
q is Mark

57:33
q is empty

57:46
I volunteer for MyData and A New Governance

58:04
I also volunteer for MyData and A New Governance

59:51
T-5 min

01:01:03
lets agree on next meeting's time before we end

01:01:24
ok for usecases

01:01:41
Standards for composing use case text?

01:01:53
guide?

01:02:32
Just getting back from the bar!...oops, quarantine

01:02:39
“Doodled out” <=== It’s.a new coronavirus symptom

01:02:47
haha

01:02:49
I'll live with this time

01:03:03
ok

01:03:06
it's later from next week because of daylight savings :(

01:03:07
thank you it’s appreciated

01:03:17
but better than 3am!

01:03:24
ok!

01:03:31
Thanks Everyone!

01:03:33
4pm ET Thursday

01:03:38
Thank you!

01:04:05
ciao!