You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arguably everything should depart from GitHub. So, I'd be ok with this change, however, I'd like solidproject.org to publicise a persistence policy. This is not only important for the spec but everything else I think. Even if it is a few simple statements indicating near future commitments about the /path/to/spec [*] , domain name (which entity is governing... and what happens if...) that'd be important. I'm not suggesting a legal-speak document.
That aside, I've discussed some level of persistence through third-parties eg. w3id.org, in chats. Perhaps that's something to consider and have it redirect to the solidproject.org. I'm not crazy about this but mentioning it again so that we don't take persistence for granted.
[*] Note that the URL Template should factor in the publication of other specs nearby the Ecosystem document. So, possibly along the lines of /spec/{name}/
@akuckartz Indeed that'd be the top candidate but I don't think the specs that we're producing at this time can be part of the paths that W3C will promise to keep around long term. It is more likely that the Solid Terms ns will be. See also https://www.w3.org/Consortium/Persistence . Perhaps @timbl or someone else can confirm?
No description provided.
The text was updated successfully, but these errors were encountered: