@hongminhee@hollo.social · Reply to silverpill
@silverpill Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!
1 reply
@trwnh@mastodon.social · Reply to 洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee @silverpill i'm not sure what the "canonical" identifier would be for a FEP; currently there is no canonical identifier. there is the codeberg repo and there is the w3id.org purl service from 888d and there is also the newer codeberg.page site
re: 888d itself the FEP is near finalization, pending some open questions about what finalization means https://socialhub.activitypub.rocks/t/fep-888d-using-w3id-org-fep-as-a-namespace-for-extension-terms-and-for-fep-documents/3098/55
the w3id.org htaccess could be updated to point at fediverse.codeberg.page if there are less issues with that, tho
socialhub.activitypub.rocks
FEP-888d: Using w3id.org/fep as a namespace for extension terms and for FEP documents
i think it could be brought to FINAL if there are no objections remaining. of course being FINAL doesn’t mean the .htaccess redirects can’t be updated in the future; the scope of this proposal is simply to have the redirects be managed by w3id. in a practical sense we have some feedback from @eprodrom that codeberg’s reliability has been somewhat low. if there are better destinations to host a copy of the repo, now would be the time to suggest them. a deploy hook could be configured on the fep ...