eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

225
active users

#rdfa

0 posts0 participants0 posts today
JG10<p>I've started a draft spec defining high level processing and rendering rules to bind an RDF graph to HTML elements. </p><p>The UI data binding is specified using HTML attributes, which when hydrated provides valid RDFa. </p><p>The idea is to enable bringing pages of data together within a single document</p><p>Still early days, but here's the description of a subject-connected list</p><p><a href="https://jg10.solidcommunity.net/open-with/rdf-ui-binding.html#subject-connected-list" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jg10.solidcommunity.net/open-w</span><span class="invisible">ith/rdf-ui-binding.html#subject-connected-list</span></a></p><p><a href="https://mastodon.social/tags/LinkedData" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinkedData</span></a> <a href="https://mastodon.social/tags/RDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDF</span></a> <a href="https://mastodon.social/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a> <a href="https://mastodon.social/tags/SolidProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SolidProject</span></a> <a href="https://mastodon.social/tags/PodOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PodOS</span></a></p>
Auden in Austria Digital<p>Very happy about the opportunity to get feedback from the <a href="https://fedihum.org/tags/RSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSE</span></a> community at <span class="h-card" translate="no"><a href="https://fedihum.org/@dhtech" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dhtech</span></a></span> Symposium (Mon, 14 July, 1:30-6pm) during <a href="https://fedihum.org/tags/dh2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dh2025</span></a>. 👩‍💻 👨‍💻 🔧 </p><p>🐍 “tei-rdfa: A Python Utility for Extracting RDFa Data from TEI-XML Documents”</p><p>🌐 <a href="https://dh-tech.github.io/2025/06/04/digital-humanities-tech-symposium-agenda/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dh-tech.github.io/2025/06/04/d</span><span class="invisible">igital-humanities-tech-symposium-agenda/</span></a></p><p><span class="h-card" translate="no"><a href="https://fedihum.org/@ACDHCH_OeAW" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ACDHCH_OeAW</span></a></span> <span class="h-card" translate="no"><a href="https://bird.makeup/users/oeaw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oeaw</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.science/@fwf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fwf</span></a></span> <span class="h-card" translate="no"><a href="https://adho.org/@adho.org" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>adho.org</span></a></span> <span class="h-card" translate="no"><a href="https://hcommons.social/@TEIConsortium" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TEIConsortium</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@dh2025" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dh2025</span></a></span> <span class="h-card" translate="no"><a href="https://fuzzies.wtf/@altbot" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>altbot</span></a></span> </p><p><a href="https://fedihum.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://fedihum.org/tags/DigitalHumanities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalHumanities</span></a> <a href="https://fedihum.org/tags/DH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DH</span></a> <a href="https://fedihum.org/tags/TEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEI</span></a> <a href="https://fedihum.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://fedihum.org/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a></p>
Auden in Austria Digital<p>📢 Releasing tei-rdfa (beta)</p><p>▶️ Python utility for extracting RDFa data from TEI-XML documents<br>▶️ Resolves native TEI namespace formatting (through &lt;prefixDef&gt;)</p><p>🌐 <a href="https://pypi.org/project/tei-rdfa/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">pypi.org/project/tei-rdfa/</span><span class="invisible"></span></a><br>🌐 <a href="https://github.com/timofruehwirth/tei_rdfa" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/timofruehwirth/tei_</span><span class="invisible">rdfa</span></a></p><p>We welcome beta testing, feedback &amp; contribution via <a href="https://fedihum.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHub</span></a>.<br>Boosts will be very much appreciated.</p><p><span class="h-card" translate="no"><a href="https://fedihum.org/@ACDHCH_OeAW" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ACDHCH_OeAW</span></a></span> <span class="h-card" translate="no"><a href="https://bird.makeup/users/oeaw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oeaw</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.science/@fwf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fwf</span></a></span> <span class="h-card" translate="no"><a href="https://hcommons.social/@TEIConsortium" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TEIConsortium</span></a></span> <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span> <span class="h-card" translate="no"><a href="https://hcommons.social/@hcayless" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>hcayless</span></a></span> </p><p><a href="https://fedihum.org/tags/TEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEI</span></a> <a href="https://fedihum.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://fedihum.org/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a> <a href="https://fedihum.org/tags/SemanticWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SemanticWeb</span></a> <a href="https://fedihum.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://fedihum.org/tags/DH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DH</span></a> <a href="https://fedihum.org/tags/DigitalHumanities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalHumanities</span></a> <a href="https://fedihum.org/tags/DigitalEdition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalEdition</span></a> <a href="https://fedihum.org/tags/SDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SDE</span></a> <a href="https://fedihum.org/tags/DSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DSE</span></a></p>
Auden in Austria Digital<p>We are super excited to go to <a href="https://fedihum.org/tags/Lisbon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lisbon</span></a> for <a href="https://fedihum.org/tags/DH2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DH2025</span></a> &amp; have the chance to talk about "Formalizing &lt;interp&gt;retation in <a href="https://fedihum.org/tags/TEIXML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEIXML</span></a> through <a href="https://fedihum.org/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a>". 🤩</p><p><span class="h-card" translate="no"><a href="https://fedihum.org/@ACDHCH_OeAW" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ACDHCH_OeAW</span></a></span> <span class="h-card" translate="no"><a href="https://bird.makeup/users/oeaw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oeaw</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.science/@fwf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fwf</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@dh2025" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dh2025</span></a></span> <span class="h-card" translate="no"><a href="https://hcommons.social/@TEIConsortium" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TEIConsortium</span></a></span> <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span></p>
Seirdy<p>The four most popular ways to use RDF-based metadata on websites are RDFa-Core, RDFa-Lite, Microdata, and inline JSON-LD.</p><p>I can’t use RDFa-Lite because I need <code>rel</code> HTML attributes. <a href="https://www.ctrl.blog/entry/rdfa-link-attributes.html" rel="nofollow noopener" target="_blank"><code>rel</code> silently upgrades RDFa-Lite to RDFa-Core</a>, which parses differently. I doubt all parsers upgrade correctly; some will try to parse RDFa-Core as RDFa-Lite. Conformant RDFa parsers upgrade RDFa-Lite pages to RDFa-Core despite many authors only being familiar with RDFa-Lite. I suppose resources like <a href="http://Schema.org" rel="nofollow noopener" target="_blank">Schema.org</a> and Google’s documentation only documenting RDFa-Lite markup worsens the confusion.</p><p>With RDFa split between two incompatible alternatives with a confusing upgrade mechanism, the alternatives are Microdata and JSON-LD. I use structured data extensively; JSON-LD would duplicate most of the page. Let’s use <a href="https://seirdy.one/posts/2024/05/30/google-document-warehouse-api-docs-leak/" rel="nofollow noopener" target="_blank">this relatively short article</a> as an example. <a href="https://github.com/scrapinghub/extruct" rel="nofollow noopener" target="_blank">Exruct</a> can convert the embedded Microdata into a massive JSON document featuring JSON-LD. <a href="https://paste.sr.ht/~seirdy/7db88ad2405d4ab685130cd513cd9defafd9d2cf" rel="nofollow noopener" target="_blank">Take a look at the JSON-LD and HTML side by side</a>. Microdata attributes take a fraction of the footprint, encode the same information, and don’t require duplicating nearly the entire page.</p> <p>Originally posted on <code>seirdy.one</code>: <a href="https://seirdy.one/notes/2024/12/13/why-i-choose-microdata/" rel="nofollow noopener" target="_blank">See Original</a> (<a href="https://indieweb.org/POSSE" rel="nofollow noopener" target="_blank">POSSE</a>). <a class="hashtag" href="https://pleroma.envs.net/tag/microdata" rel="nofollow noopener" target="_blank">#Microdata</a> <a class="hashtag" href="https://pleroma.envs.net/tag/semanticweb" rel="nofollow noopener" target="_blank">#SemanticWeb</a> <a class="hashtag" href="https://pleroma.envs.net/tag/rdfa" rel="nofollow noopener" target="_blank">#RDFa</a> <a class="hashtag" href="https://pleroma.envs.net/tag/html" rel="nofollow noopener" target="_blank">#HTML</a></p>
Auden in Austria Digital<p>📢 Looking for your support:</p><p>We seek the feedback of <a href="https://fedihum.org/tags/DH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DH</span></a> <a href="https://fedihum.org/tags/CH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CH</span></a> <a href="https://fedihum.org/tags/SDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SDE</span></a> <a href="https://fedihum.org/tags/DSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DSE</span></a> practitioners on our approach to formalizing scholarly interpretation in <a href="https://fedihum.org/tags/TEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEI</span></a> <a href="https://fedihum.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> through <a href="https://fedihum.org/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a>. </p><p>🌐 <a href="https://github.com/auden-in-austria-digital/aad-data/discussions/42" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/auden-in-austria-di</span><span class="invisible">gital/aad-data/discussions/42</span></a> </p><p>We will be extremely thankful for your feedback &amp; suggestions.</p><p><span class="h-card" translate="no"><a href="https://fedihum.org/@ACDHCH_OeAW" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ACDHCH_OeAW</span></a></span> <span class="h-card" translate="no"><a href="https://bird.makeup/users/oeaw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oeaw</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.science/@fwf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fwf</span></a></span> <span class="h-card" translate="no"><a href="https://hcommons.social/@TEIConsortium" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TEIConsortium</span></a></span> <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span> </p><p><a href="https://fedihum.org/tags/DigitalEdition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalEdition</span></a> <a href="https://fedihum.org/tags/SemanticWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SemanticWeb</span></a> <a href="https://fedihum.org/tags/RDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDF</span></a></p>
Auden in Austria Digital<p>Working, for the first time, w/ <a href="https://fedihum.org/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a> in a <a href="https://fedihum.org/tags/TEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEI</span></a> / <a href="https://fedihum.org/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> framework, one question has popped up:</p><p>is it required/standard/good practice to hierarchically nest the elements carrying the `property` attribute (for RDF predicates) w/i the element carrying `about` (for the RDF subject); and those carrying `resource` (for RDF object) w/i the `property` elements? Or is it a question of element sequence?</p><p><span class="h-card" translate="no"><a href="https://fedihum.org/@ACDHCH_OeAW" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ACDHCH_OeAW</span></a></span><br><span class="h-card" translate="no"><a href="https://w3c.social/@csarven" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>csarven</span></a></span><br><span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span></p>
Nicol Wistreich<p><span class="h-card" translate="no"><a href="https://mastodon.social/@egonw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>egonw</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@eloquence" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>eloquence</span></a></span> sounds maybe harder to govern than already dodged cross-border tax. CC also seems to have resisted adding clauses to help define commercial use. I only know of <a href="https://social.coop/tags/CCRel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCRel</span></a> (<a href="https://wiki.creativecommons.org/images/d/d6/Ccrel-1.0.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wiki.creativecommons.org/image</span><span class="invisible">s/d/d6/Ccrel-1.0.pdf</span></a>), which built on Aaron Swartz's <a href="https://social.coop/tags/RDFa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDFa</span></a> syntax for CC licenses, to let people construct &amp; define more complex rights docs: "publishers can use ccREL descriptions in combination with<br>additional attributes taken from other publishers, or with entirely new attributes", but not heard of its use.</p>