Releasing tei-rdfa (beta)
Python utility for extracting RDFa data from TEI-XML documents Resolves native TEI namespace formatting (through <prefixDef>)
https://pypi.org/project/tei-rdfa/ https://github.com/timofruehwirth/tei_rdfa
We welcome beta testing, feedback & contribution via #GitHub.
Boosts will be very much appreciated.
@Seirdy Hope I understood you correctly; not trying to change your mind:
Unless you've already checked w/ other #RDFa parsers, I wouldn't rely on GRRT (referenced blog post). AFAICT, GRRT wasn't parsing the HTML snippet correctly back then nor now for that HTML snippet.
If you don't use the `vocab` attribute, values like `license` are ignored by the RDFa parser (unless host language's default vocab is applied). For anything else parsing plain ol' rel=license, that's not an issue anyway.
My approach:
* all human-readable information is visible and actionable in markup languages (HTML, SVG, MathML..)
* anything significant has a URI and machine-readable.
For my purposes, publishing various types of content and working on an application ( https://dokie.li/ ) - it comes down to using the full expressivity of #RDFa.
Why RDFa: https://csarven.ca/linked-research-decentralised-web#why-rdfa
The four most popular ways to use RDF-based metadata on websites are RDFa-Core, RDFa-Lite, Microdata, and inline JSON-LD.
I can’t use RDFa-Lite because I need rel HTML attributes. rel silently upgrades RDFa-Lite to RDFa-Core, 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 Schema.org and Google’s documentation only documenting RDFa-Lite markup worsens the confusion. Update 2024-12-16: Sarven Capadisli has clarified on the Fediverse that this is the behavior of one faulty parser; rel only triggers an upgrade when used with an RDFa namespace. I may re-evaluate RDFa.
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 this relatively short article as an example. Exruct can convert the embedded Microdata into a massive JSON document featuring JSON-LD. Take a look at the JSON-LD and HTML side by side. Microdata attributes take a fraction of the footprint, encode the same information, and don’t require duplicating nearly the entire page.
Originally posted on seirdy.one: See Original (POSSE). #Microdata #SemanticWeb #RDFa #HTML
Depends :)
#RDFa tips:
* Consider how the data needs to be updated and whether this affects the markup or structure. Keep structural changes to minimal.
* Ensure all significant info is human-visible/accessible. Info should almost never be available exclusively for machines.
* Consistently use rel when the value is a URI, property when value is a literal. Makes it possible to use both rel and property together on the same element or other combinations.
...
Working, for the first time, w/ #RDFa in a #TEI / #XML framework, one question has popped up:
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?
@AAD_OeAW @w3c For online service, there is @gkellogg 's http://rdf.greggkellogg.net/distiller which I think works great for #RDFa - I've been using / poking at for improvements for some time now.
Let me know if you're looking for other services or libraries that you can use...
The @w3c #RDFa Distiller and Parser is discontinued and the underlying software no longer maintained.
https://www.w3.org/2012/pyRdfa/Overview.html
Can anyone point us to another such service (apart from #ChatGPT)?
New blog post
Building a new site! — https://mnt.io/articles/building-a-new-site/
It's time to rewrite my site from scratch. I'm nostalgic of the good old Web. This site is hand-written, and promotes smallness, speed, simplicity and fun. Let's discover the new lore (!), and let's talk about series a little bit.
Erm… concerning the `fediverse:creator` #OpenGraph tag in #Mastodon, described in <https://blog.joinmastodon.org/2024/07/highlighting-journalism-on-mastodon/>:
It's either not an OpenGraph tag (which would be unfortunate), or the example in the blog is wrong.
OpenGraph, being based on #RDFa, uses the `<meta property="…">` attribute, not `name`.
Also, if it is OpenGraph, then what namespace should I add for the `fediverse:` prefix to point to?
Which one is true for this feature, @MastodonEngineering?
@egonw @eloquence 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 #CCRel (https://wiki.creativecommons.org/images/d/d6/Ccrel-1.0.pdf), which built on Aaron Swartz's #RDFa syntax for CC licenses, to let people construct & define more complex rights docs: "publishers can use ccREL descriptions in combination with
additional attributes taken from other publishers, or with entirely new attributes", but not heard of its use.
@hrefna This would he great if we did not make the same mistake as #RDFa-Lite: there should be no way to implicitly upgrade the subset to a full JSON-LD document simply by using a feature. The fact that we are using a subset should be clear.
RDFa-Lite was DOA because any usage of link relations would silently upgrade the document to full RDFa-Core, but several Lite-only parsers still existed. It effectively made RDFa-Core hard since it could get parsed as RDFa-Lite, and RDFa-Lite hard since it could get parsed as full RDFa-Core. It killed both.
Accidentally dragged my finger too long while browsing a site via #Brave and up popped up an “inline #XBRL viewer.” Whaaaa? Then I remembered: “#RDFa for business.” Amazingly still a thing, even after 20+ years.. #SemanticWeb @semanticweb
Ok, so I think I found a #masonry #layout #template that will suit my wants. I will probably need to do some modifications to implement #microdata / #microformats ( #microformats2 ) (maybe #RDFa lite too?).
Now another big #question would be, should I use the Open #Dyslexic #typeface? #webdev #design #ux #ui #uiux https://opendyslexic.org/
