<orie> I object to the passive aggressive tone of "take a breath".
<mprorock> @brent +1 yes, that is the reference
<by_caballero> Authorization is HARD
<tallted> "in the course of implementation and writing implementation guide, we found need for this extension, that clarification, this radical change" is all good
<mprorock> I am glad to hear I am not the only person with chickens in the background
<orie> agree with Juan... folks who come from a vertical need a softer landing spot.
<by_caballero> "landing spot"
<orie> I can live with implementation guide, as long as we can define API Endpoints and Authorization.
<by_caballero> "traceability onramp"
<kim> when does something need to be a CCG work item? What do the participants get out of it, and what does the CCG get out of it? There has been a touch of "move fast act questions later" attitude in discussions around this work item, which runs counter to the ability of others to contribute
<orie> "traceability new world order"
<kim> I think that IPR protection is what the participants get out of it, but that also puts a burden on the community to make sense of it
<wayne_chang> Traceability Ecosystem Schematics
<wayne_chang> but less clumsy
<bengo> eg publishing a Note vs a CR
<orie> Traceability API might become DIDComm + PE
<orie> it might look radically different than VC HTTP API
<orie> or not....
<wayne_chang> Traceability Recipe Book
<cel> Traceability Profile?
<wayne_chang> ooh, profile
<agropper> How many ways can we talk about APIs without using the word "authorization??
<orie> authorization... not authentication.
<dmitriz> the PROV-O provenance ontolgoy has to do with provenance of ideas/creative works. Not in the sense that the Traceability cohort is using it
<tallted> PROV-O covers brick-and-mortar as well. Speaking as one of those involved in that WG.
<orie> We have touched Provenance
<orie> regarding the VC topic of Evidence
<orie> Spherity in particular
<orie> has contributed to this
<orie> "don't ask us no not use DIDs and VCs"
<orie> not "don't ask questions"
<orie> There is a new DIF work item, which essentially covers the same space... APIs for Presentation Exchange... I'm trying to keep things aligned.
<heathervescent> Wayne, we can kick the IIW conversation to next week if you like
<wayne_chang> Sure, that sounds good heather, thanks
<orie> IMO the IIW conversation is the same conversation... its about how to do interoperability
<orie> in the open.
<orie> we made significant progress on this topic.
<orie> at IIW
<wayne_chang> @Orie there were some sessions at IIW not explicitly focused on technical interoperability that could be good to discuss too
<by_caballero> I would add that authorization and AUDIT were key themes at IIW this time around-- and I was here for it!
<kim> Manu - that's not why it's frustrating
<kim> We are super comfortable with path blazing, I assure you
<orie> CCG has process for having regular calls... and repos... same as DIF, and OIDF.
<orie> the work isn't going anywhere else
<orie> but the work will happen elsewhere for sure.
<orie> we can't avoid that.
<orie> the W3C isn't the only place where these topics are addressed.
<tallted> (DRM = Digital Rights Management)
<kim> "there was a choice" <-- can you give more context for that Manu?
<by_caballero> landing spot was a really good point Orie made-- i would love it if VC-HTTP-API's repo even pointed to more specific implementation guides and/or beginner's guides (including the CCG101 material, etc)
<by_caballero> s/ even/just/
<orie> I object to what heather is saying... we have always done our traceability work in the open in github.
<orie> we use the tools the working group provides
<justin_r> a huge +1 to Heather's point just now.
<kim> She's correct -- whatever is in github is just a flattening of hours and hours of conversations that no one else is privy to. Also, private slack groups for those members
<orie> ^ yep, need public meetings with minutes to solve that
<mahmoud_alkhraishi> is there a traceability api ( or w.e we're calling it) call today?
<kim> I tried to join that slack group to get more context and was rejected
<heathervescent> Oh yeah, is there a traceability call today?