[media-types] Re: [IANA #1449861] text/vnd.longform registration request
"Murray S. Kucherawy" <[email protected]> Tue, 14 Apr 2026 21:41:17 -0700
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CAL0qLwZEKh+=ZXHCJqYg3F0rY+zqZcGWtJALbpBPa_7GaPk87A@mail.gmail.com> |
On Tue, Apr 14, 2026 at 3:55 PM Amanda Baber via RT < [email protected]> wrote: > Response from the applicant: > > === > > Yes there is a product. It is not described in my README yet but I have an > open source project https://codeberg.org/occultist/octiron, still > pre-alpha, > which server renders and picks up the pieces of rendered Longform. > It is a concrete implementation of the theoretical application described > in my Longform spec document. > > This is part of a larger open source project I'm calling Occultist.dev > that the code-bases here https://codeberg.org/occultist all support, > Octiron and Longform are primary components. > > If things work out this would compete with the likes of Next.JS and other > server rendereable Javascript frameworks. > > Both Octiron and Occultist.dev could be considered opensource products. > They are not well documented yet as content negotiation is a large part of > how they work > and I wanted to lock down Longform's media type before I started > documenting and promoting the solution. > > Given this I think "text/vnd.longform" might be more suitable given I plan > to foster a adoption around the wider project and that Octiron is publicly > available, albeit not production ready. > > === > > Which prefix should be used here? > > If vendor tree is OK, does it need any other changes? > Vendor is fine. I just wanted to have the discussion. Approved as requested. -MSK _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]