Alex_Tweeddale: Yep I'm here Anchor Great yeah if you have any questions at any point just you can just pass to me I'll also keep an eye on the chat to see if anything comes through and then I'll just bring it up if it does. ✪
<manu_sporny> Shout out to Blacksburg, VA!!! (in the example) :P
<bumblefudge> My favorite kind of behavior-- undefined behavior!
<manu_sporny> it's the spice of life, bumblefudge! :P
Alex_Tweeddale: Yeah I second that Marcus and Carly who Tema did a really good presentation in trust over IP called pids with did switch was looking at like research identifiers which are traditionally identified using my persistent identifiers and we both looked at how that could be augmented with using a did length resource or a piston did URL so I 100% would love to sort of explore that use case a bit further but yeah I'll pass it back over to anchors to sort of kick off the second half here. ✪
Alex_Tweeddale: Just going to pause that cuz I'm a man who has his hand up so. ✪
<bumblefudge> id array?
Alex_Tweeddale: I think just to pause that and I may be wrong here anchor but if you called it just type then if you were doing some sort of query syntax that could get confused with maybe something like service type which is also called type so if you are querying a did documents in just wanted to find just wanted to clear by resource type and I think having a unique delineation between resource type and other different types within the date document could be a useful thing to have but I might be wrong. ✪
<alex_tweeddale> Ah sorry Dmitri, I'll pause for you in a sec
Alex_Tweeddale: Yeah Dimitri had his hands up a bit earlier so I think we'll pass over to Dimitri. ✪
Alex_Tweeddale: We actually have done that so I think anchor maeby was referring to a way we did it previously but then we had we did update it to also known as because we definitely looked at that same energy. ✪
Alex_Tweeddale: May I see your hand if I just want to add one more point that quickly I think in the service section as well you're quite limited and what the fields are so you've obviously got the ID and the type but what we do in the resource metadata is we derive uniqueness from resource name and resource type so if you were trying to lay this out in the service section you might run into challenges with previous and next versions of the same resource because you wouldn't be able to necessarily advertise. ✪
Alex_Tweeddale: add to research to resources in the service section with the. ✪
Alex_Tweeddale: In the same type because you might face a collision where the fragment in the in the ID was the same you wouldn't be you wouldn't allow that to happen so you would only be able to point to one specific version of a particular resource in time which is where I think this is a bit stronger in terms of being able to semantically point to the next and previous versions man you are I'll go to you next. ✪
Alex_Tweeddale: When we were proposing this work item there was also some like discussion around other implementations of our habits was working I see Joe Andrew you on the call I was wondering if you see or any like a lot of synergies between this approach in your approach and maybe how you thought about this going forward as well in conjunction with what you've already done. ✪
Alex_Tweeddale: I see you come off mute Joe but I can't hear you. ✪
<manu_sporny> having a "never changing" unique ID might create problems if its mutable, is what I think Joe is saying (and I agree with him at a high level).
<manu_sporny> Though, I'm concerned that I'm missing nuances that the cheqd team hit in their design.
Alex_Tweeddale: What's that just kind of closing thoughts as were at the our I just wanted to say Manu others if you want to sort of play around with did link to resources and test our theories in practice it's like a Sandbox environment this is all available currently use on checks may not and test now so if you want to get set up and play around with it and test some hypotheses happy to help there as well. ✪
<manu_sporny> Awesome, thanks AlexT -- I'm time starved right now, but very interested in the work.
<harrison_tang> Thank you, Ankur and Alex! Love the presentation.