Open TallTed opened 2 years ago
In any case, they're all inferior to USS...
Enterprise (NCC-1701-D)
You might want to have a look over https://github.com/solid/deit/issues .. https://github.com/solid/deit/issues/15 seems relevant.
Related issue: https://github.com/solid/community-server/issues/908
So far as I can tell, neither of those related issues has yet resulted in a PR?
So, yes, related, similar, even same, idea as those others.
I have made this Glossary as a first approach. Is this usable (must be improved a lot) ? Shall I link it to https://github.com/solid/solidcommunity.net README ?
@bourgeoa -- I think you left out the link to your first approach?
https://github.com/solid/solidcommunity.net/wiki/Glossary. Above message updated
@bourgeoa -- Definitely a good start! I think it ought to be linked from the READMEs of https://github.com/solid/solidcommunity.net and all the other Solid projects, among other places.
If I find some spare minutes, I will try to remember to come make some tweaks (such as cross-references between solid-server [the generic] and the specific implementations listed [CSS, ESS, NSS, PSS]; normalizing some capitalizations [such as IdP, WebID]; and adding NSS to the list)... Even better if someone else gets to making these before me!
I have been working on this for months. I'm not done but have put up what I have so far. Please see https://github.com/solid/deit/issues/15#issuecomment-948094755amd provide feedback.
There are too many acronyms flying around Solid, without clear expansions in the Solid Community README or anywhere else easily discoverable (or I probably wouldn't be logging this issue).
I've been involved since very near the inception of Solid, and I still can't easily remember what these expand to, especially with all the TLA collisions involving CSS, NSS, PSS, ESS, etc.
At a minimum, I'm hoping for a short list of the various
*SS
and their Solid-relevant expansions, to be added to the README on solidcommunity.net, and hopefully echoed in all the repos where multiple*SS
may be discussed. Getting into the habit of expanding these, and/or linking to the list of expansions, at least on first usage on any given issue, would be very helpful!