ACE (Atom Centric Elevation)

[sjehuda]

This is an idea which I have thought of and realized last friday.

ACE (Atom Centric Elevation) is a standard for publishing contents in an accessible, syndicated, and structural fashion, by means of enumerating of items, being an essential part of the proper eutrophy of publishing platforms; The standard is comprised by these XML technologies.

gemini://woodpeckersnest.space/~schapps/journal/2025-07-29-announcing-ace.gmi

https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/journal/2025-07-29-announcing-ace.gmi

Even though the Rivista publishing system site does produce XHTML files, it is really based on Atom Syndication Format, and thre are optional XML files such as OPML. Sitemap and Urlset that may be utilized for mapping and navigation of pages, which means that ACE sites are even usable over ADC, BitTorrent, eDonkey2000 Gnutella, IPFS and other P2P systems.

https://journal.woodpeckersnest.eu/v

https://journal.woodpeckersnest.eu/v?atom

gemini://journal.woodpeckersnest.eu/v

---

UPDATE: Since I have posted the first message, I have updated the specification to include navigational instructions inside "atom:link", so files such as Sitemap and Urlset are optional.

[lwindolf]

As I understand it the idea is more or less using Atom as the "storage" format of a website structure and have a browser/other client render the Atom on the fly?

[sjehuda]

The example is deliberately about other protocols, because it is obvious that HTTP does it also.

So, HTTP can do this, yet HTTP is centralized, and several american organizations abuse their "free" HTTP products in their favour.

The purpose of Ace, is to utilize Atom files over any protocol, and also offline.

---

Do notice, that HTML could have been a general filetype for documents, yet some organizations do not want people to consider HTML as an offline document and as an alternative to DOC, DOCX, ODT, RTF, et cetera.

Atom could be "the new PDF" for universally viewable documents.

[lwindolf]

I think I get it now.

[sjehuda]

Lars. Good day.

Please refer to articles at https://journal.woodpeckersnest.eu/posts/ and observe the links "previous" and "proceed" at the bottom of each article.

These are generated by urlset.xml (part of sitemap.xml), yet it will be changed in favour of instructions from "atom:link" for accuracy.

I have further added new directives to handle rel="related" of "atom:link" as a new section which be called "Related". It will be realized in next server update.

With an XSLT stylesheet very page is entirely sourced from Atom Syndication Format.

Please also refer to page https://journal.woodpeckersnest.eu/help/rss/ and approve the resources for Liferea.

[lwindolf]

The Liferea entry on https://journal.woodpeckersnest.eu/help/rss/ looks fine to me.

I understand the "Next" / "Proceed" links. What about following the existing HTML standards with

<link rel="next" ...>
<link rel="prev" ...>

in the HTML document head (https://developer.mozilla.org/de/docs/Web/HTML/Reference/Attributes/rel#next)?

[sjehuda]

in the HTML document head
(https://developer.mozilla.org/de/docs/Web/HTML/Reference/Attributes/rel#next)?

I did not know of attribute "next".

I understand the "Next" / "Proceed" links. What about following the
existing HTML standards with

These are utilized as directives for the client (i.e. Liferea), to realize next and previous buttons, as do document and ebook readers such as Atril, KchmViewer, and Okular.

In this case, it is used as a directive for the XSLT stylesheet to realize these as navigation links to specified IRI/URI/URL.

<nav id="xslt-navigation-posts">
    <xsl:for-each select="atom:entry/atom:link[@rel='navigation']">
        <xsl:if test="@title='previous'">
            <span id="xslt-navigation-previous">
                <xsl:element name="a">
                    <xsl:attribute name="href">
                        <xsl:value-of select="@href"/>
                    </xsl:attribute>
                    <xsl:text>&lt; &lt; </xsl:text>
                    <xsl:value-of select="@title"/>
                </xsl:element>
            </span>
        </xsl:if>
        <xsl:if test="@title='proceed'">
            <span id="xslt-navigation-proceed">
                <xsl:element name="a">
                    <xsl:attribute name="href">
                        <xsl:value-of select="@href"/>
                    </xsl:attribute>
                    <xsl:value-of select="@title"/>
                    <xsl:text> &gt; &gt;</xsl:text>
                </xsl:element>
            </span>
        </xsl:if>
    </xsl:for-each>
</nav>

Because I intend for "Ace" to be cross protocol, these links could also
be ed2k, magnet, ftp, gemini, gopher, et cetera.