csarven on main
Add server-auxiliary-resources-… Apply suggestions from code rev… Clarify server-auxiliary-resour… and 2 more (compare)
csarven on server-link-auxiliary-type
Make server-auxiliary-resources… (compare)
@agentydragon_gitlab Generally questions like these (that do not pertain to defining the Solid Specification) are best placed in https://gitter.im/solid/chat. In any case, the interface you're looking at at solidcommunity.net is called mashlib (sometimes called "The Data Browser" or "SolidOS"), and bug reports for it go here: https://github.com/solid/mashlib/issues/
(Yes, it's all a bit confusing that there are so many different projects, but that's what you get if you have an open standard that everyone can implement :) )
@/all Meeting with the CredentialsCG is fixed to March 10 at 15:00 UTC and 18:00 UTC (two ~1h sessions) - seems to work for most. CCG presents to SocialCG in the first session, and the other way around in the second session.
They've suggested that an intro to their following work items would be of interest to us: Universal Wallet, DID-Core, Secure Data Storage + others. Also asking any specific work items or areas they should cover.
Please share (here) what you'd like to learn more about.. I'll collect the responses here and send. In https://gitter.im/solid/specification?at=6001ada781c55b09c70d2da8 I suggested some areas:
Identity/Identifiers: WebID, DID
Access control / Capability-based security models: ACL, OCAP
VC data model
All sorts of Security and Privacy Considerations
I think we should definitely hear more about the security models they're working on. I'm not sure about "Universal Wallet" (as per their suggestion) at this time - not sure if that's high priority.. but I have no strong opinion otherwise.
Are the bookmarks etc in the Specs going to persist - or are they not reliable as URI references to mission critical system specs?
Yes, intended to "persist". In a long enough time, probably not. I've created/proposed a pledge for URI persistence from for the technical reports under solidproject.org: solid/solidproject.org#489 -- you'll have to follow-up on the linked issues.. Can discuss finer details.
I would however take the current state as draft - re "Editor's Draft" as far as the Status of the Document goes. So, expect changes.. there are some units of information that I didn't get to which will probably get renamed.
Regarding your intentions/needs, I have my full support. This is also something that CSS is doing/will do eg. referencing distinct requirements in context of the code that's implementing it.
Maybe I'm asking for something different - a reliable master index of URI's for all the solid specs and their sections
You'll get that eventually re "reliable". See for example: http://rdf.greggkellogg.net/distiller?command=serialize&url=https:%2F%2Fwww.w3.org%2FTR%2Fldn%2F&format=rdfa&output_format=turtle&raw -- W3C's snapshot is frozen.. That's the URI-R (Original Resource).. URI-M is https://www.w3.org/TR/2017/REC-ldn-20170502/ (the URI that W3C pledges for persistence). See PR 489 above.
Good news everyone!
We're (again) in contact with the W3C Web Platform Incubator CG and this time we're looking into exchanging our notes/work over a meeting:
I've mentioned WICG's work/initiative around "WebID" in the authentication-panel awhile back:
February 22 (Monday) at 17:00 GMT (for a ~2h session, TBD) is the proposed date for the meeting.