3 ms·
Except a URL only points to one resource. The idea here is that this identifier would exist on any resource related to PEP (maybe even in URLs).
by wtetzner 6y ago
Except a URL only points to one resource. The idea here is that this identifier would exist on any resource related to PEP (maybe even in URLs).
- deleted 6y ago[deleted]
- fiddlerwoaroof 6y agoThat’s not a problem, you just add a meta or a link tag that points to “the” url for your project (maybe og:app-id Or a link with rel=“app”)
- notatoad 6y ago>Except a URL only points to one resource isn't that exactly what this is asking for though? A URL can by definition only point to one resource. So if you include that URL with every other reference to the project (in the app descriptions, blog posts about it, etc) then you always know you're talking about the same thing. It makes a lot more sense that any resource related to this PDF editor should include a link to "https://macpep.org https://macpep.org" instead of including some random 128 character string. Any resource related to python peps should include a link to "https://www.python.org/dev/peps/ https://www.python.org/dev/peps/" (which all PEPs do, by virtue of having a url that's a subdirectory of the PEP index URL)