#rdfa — Public Fediverse posts

I've started a draft spec defining high level processing and rendering rules to bind an RDF graph to HTML elements.

The UI data binding is specified using HTML attributes, which when hydrated provides valid RDFa.

The idea is to enable bringing pages of data together within a single document

Still early days, but here's the description of a subject-connected list

https://jg10.solidcommunity.net/open-with/rdf-ui-binding.html#subject-connected-list

#LinkedData #RDF #RDFa #SolidProject #PodOS

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

@jakintosh I kinda lost interest when #HTML5 came out and was presented as the pragmatic answer to the strictly validated #XHTML. With that we lost namespaces. Sure #RDFa introduced it somewhat, but in an ugly way. I was hoping the future would be <title><dc:title>My blog</dc:title></title>, where RDF would just be mixed in with #HTML. So yeah, also SVG embeds would have been namespaced when mixed in HTML docs. RDFa was supposed to be a pragmatic variant but made metadata a second class citizen. JSON LD is basically the old approach of linking outside for metadata, which is perhaps the worst… so I am now like. Call me when XHTML2 is a thing 😅

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/

OpenWeb-Notizen: XAuth, OExchange, Firefox Sync, RDFa

Chris Messina erklärt XAuth
XAuth ist eine Art Cross-Domain Cookie mit dem man Versucht die Flut an Share, Like und Login Icons auf ein Minimum zu reduzieren.

Hier klicken, um den Inhalt von Vimeo anzuzeigen.
Erfahre mehr in der Datenschutzerklärung von Vimeo.

Inhalt von Vimeo immer anzeigen

» XAuth – an introduction
» Offizielle XAuth Seite

OExchange einfach erklärt
OExchange ist ein offenes Protokoll um eine beliebige URL mit einem beliebigen Service im Web zu teilen. Die Demo zeigt die Funktionsweise von OExchange und welche Vorteile sich in Kombination mit z.B. XAuth ergeben.

Hier klicken, um den Inhalt von YouTube anzuzeigen.
Erfahre mehr in der Datenschutzerklärung von YouTube.

Inhalt von YouTube immer anzeigen

» OExchange in action
» Offizielle OExchange Seite

Firefox Sync
Mozilla benennt das Labs-Projekt Weave Sync in Firefox Sync um und kündigt an, den Sync-Mechanismus in eine der nächsten Firefox Versionen fest zu integrieren. Im Zuge meiner Recherche bin ich außerdem noch auf einen Wiki-Artikel gestoßen, der erklärt wie man den Firefox Sync zukünftig auch mit OpenID oder OAuth koppeln könnte:

The user must have a way of proving to a third-party service that they really are who they claim, and for the Mozilla service to provide information back to the third-party service that access has been granted. The OpenID and OAuth protocols provide what we need here, and the OpenID/OAuth hybrid flow has been described.

Once this is done, the third party service will be able to establish a relationship with the Weave Sync service for a user, without the user disclosing his or her password.

» Stay in Sync With Your Firefox
» Firefox Sync Graduates from Mozilla Labs
» Secure Data Sharing

RDFa 1.1 – Alles neu, alles anders
Dank HTML5 (ohne X) wurde RDFa noch einmal grundlegend überdacht. In der Version 1.1 werden die RDF-Vocabularies beispielsweise nicht mehr über Namespaces definiert. Früher:

<a xmlns:cc="http://creativecommons.org/ns#"   rel="cc:license"   href="http://creativecommons.org/licenses/by-nc-nd/3.0/">a>.Code-Sprache: HTML, XML (xml)

Jetzt:

<a prefix="cc: http://creativecommons.org/ns#"   rel="cc:license"   href="http://creativecommons.org/licenses/by-nc-nd/3.0/">a>.Code-Sprache: HTML, XML (xml)

Grund der Änderung: HTML kennt im Gegensatz zu XHTML keine Namespaces und RDFa soll sowohl in HTML5 als auch in XHTML5 integriert werden.

» RDFa Core 1.1

RDFa checker
Toby Inkster hat einen sehr umfangreichen RDFa checker veröffentlicht:

It checks your web page for RDFa and displays any data found there. It also compares your data against the published recommendations from major consumers/users of RDFa data, to see how well your data matches their requirements.

» check rdfa

#Firefox #NASCARProblem #OAuth #OExchange #OpenID #RDFa #sync #Video #XAuth

https://notiz.blog/b/kk