Guidelines for publishing, discovering and using URI Persistence policies

As per https://www.w3.org/TR/webarch/#URI-persistence

URI persistence is a matter of policy and commitment on the part of the URI owner.

Going forward, it would be in the interest of Solid servers - pods - to make their URI Persistence policy available as Linked Data. Applications can discover these policies and bring them to the attention of their users eg. bringing the policy to the forefront before committing to any action, like creating a pod or any resource within, as well as automate decisions on behalf of their users' based on their preferences.

Typically they describe the following:

• a pledge towards the longevity and accessibility of the URIs;
• what happens to the URIs once the owner ceases to exist or owners are changed.

The Solid Ecosystem or possibly the Best Practices and Guidelines document can cover this.

Policies can be expressed in different ways to suit each site's / URI owners' pledge. Here is a famous persistence policy from W3C: https://www.w3.org/Consortium/Persistence

Another example discoverable from https://csarven.ca/ and available in RDF:

<https://csarven.ca/>
  <http://www.w3.org/2000/10/swap/pim/doc#persistencePolicy> <https://csarven.ca/about#persistence-policy> .

<https://csarven.ca/about#persistence-policy>
  <http://schema.org/name> "URI Persistence Policy"@en ;
  <http://schema.org/description> "..." .

The persistence policy resource can of course be extended in any creative and useful way eg. including relevant provenance record (perhaps with PROV-O).

Start with the linked W3C URI Persistence reference, then review the proposed Linked Data example and the Solid Best Practices and Guidelines document mentioned in the issue. Define what a Solid server's persistence policy should disclose, how applications can discover it, and where the guidance belongs; done means the policy guidance and examples are documented and agreed.