There's now a proper rendered web interface for FEPs at `https://fediverse.codeberg.page/fep/fep/*/`, which is much nicer to read than the raw Markdown source on Codeberg.
-
There's now a proper rendered web interface for FEPs at
https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink,https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.
I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)
#fedidev #fep #fediverse #ActivityPub
-
T tag-activitypub@relay.fedi.buzz shared this topic
-
@hongminhee Content Negotiation!
-
@hongminhee It's a good idea. However, I'd like to note that w3id.org/fep/ permalinks are not canonical, they were proposed in FEP-888d but have never become "official".
-
@hongminhee@hollo.social the w3id pages point to the rendered resource afaik?
The codeberg page is nicer, but the existing pages are okay too
-
@hongminhee It's a good idea. However, I'd like to note that w3id.org/fep/ permalinks are not canonical, they were proposed in FEP-888d but have never become "official".
@silverpill@mitra.social Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!
-
@silverpill@mitra.social Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!
@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
-
@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
@hongminhee @silverpill i intend to review my submitted feps soon-ish to do some spring housekeeping, and this is definitely one of the things i want to test. iirc last i checked there were some issues with how codeberg's pages-server handled headers, but the new git-pages server seems to handle them correctly now? which is a good sign
-
@hongminhee @silverpill i intend to review my submitted feps soon-ish to do some spring housekeeping, and this is definitely one of the things i want to test. iirc last i checked there were some issues with how codeberg's pages-server handled headers, but the new git-pages server seems to handle them correctly now? which is a good sign
@hongminhee @silverpill ah, wait, i remember now -- the issue is that Codeberg Pages doesn't set CORS headers at all, which means javascript jsonld parsers like the one on the playground won't work.
although per https://codeberg.org/git-pages/git-pages#:~:text=CORS it seems that a _headers file might allow manually enabling CORS for the site?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login