#rdfa — Public Fediverse posts

OCaml-RDF 1.2.0 is out (and soon in opam)
https://www.good-eris.net/ocaml-rdf/posts/ocaml-rdf-1.2.0.html

Two main additions in this release:
- A #rdfa processor
- a new Igraph module for immutable graphs (for functional style).

#ocaml #rdf

OCaml-RDF 1.2.0 is out (and soon in opam)
https://www.good-eris.net/ocaml-rdf/posts/ocaml-rdf-1.2.0.html

Two main additions in this release:
- A #rdfa processor
- a new Igraph module for immutable graphs (for functional style).

#ocaml #rdf

@gugurumbe W3C #RDFa is what you are looking for:

* https://www.w3.org/TR/rdfa-core/
* https://www.w3.org/TR/rdfa-syntax/
* https://www.w3.org/TR/rdfa-in-html/
* https://www.w3.org/TR/xhtml-rdfa-scenarios/

@jyasskin Off topic: Not what you're looking for but in case of minor interest, and perhaps with a broader view on "accessible" to both humans and machines, see https://www.w3.org/TR/ldn/linked-data-notifications-overview.svg

You can try input format #RDFa with the URI above and output to whatever e.g., graphviz.

What interests to me about this information embedding/extraction.

That said, perhaps I can propose an update to improve the accessibility tree on that SVG.

@jyasskin Off topic: Not what you're looking for but in case of minor interest, and perhaps with a broader view on "accessible" to both humans and machines, see https://www.w3.org/TR/ldn/linked-data-notifications-overview.svg

You can try input format #RDFa with the URI above and output to whatever e.g., graphviz.

What interests to me about this information embedding/extraction.

That said, perhaps I can propose an update to improve the accessibility tree on that SVG.

RDFa Lite tries to be an "easier" subset of RDFa

RDFa is RDF encoded into HTML in a way that sort of feels like Microformats. Sort of

Of course, one question might be — easier for whom?

I think there could be an even "easier" subset of RDFa Lite that is easier for people writing parsers

Get rid of the "vocab" and "prefix" attributes, and —

Just have the "property", "resource", & "typeof" attributes

I will call this: RDFa Super Lite

#LinkedData #JSONLD #RDF #RDFa #RDFaSuperLite #RDFaLite

RDFa Lite tries to be an "easier" subset of RDFa

RDFa is RDF encoded into HTML in a way that sort of feels like Microformats. Sort of

Of course, one question might be — easier for whom?

I think there could be an even "easier" subset of RDFa Lite that is easier for people writing parsers

Get rid of the "vocab" and "prefix" attributes, and —

Just have the "property", "resource", & "typeof" attributes

I will call this: RDFa Super Lite

#LinkedData #JSONLD #RDF #RDFa #RDFaSuperLite #RDFaLite

9/

A regular users might write Markdown like this:

"""
# Hello!

How do you do?
"""

Or write HTML like this:

"""
<article>
<h1>Hello!</h1>
<p>How do you do?</p>
</article>
"""

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

9/

A regular users might write Markdown like this:

"""
# Hello!

How do you do?
"""

Or write HTML like this:

"""
<article>
<h1>Hello!</h1>
<p>How do you do?</p>
</article>
"""

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

8/

REMEMBER: this is for power-users, not regular users

How would you get ActivityPub / ActivityStreams into HTML using RDFa‽

Like this:

<div vocab="https://www.w3.org/ns/activitystreams#" typeof="Note">
<p property="name">Hello!</p>
<p>How do you do?</p>
</div>

AGAIN, REMEMBER: this is for power-users, not regular users.

Regular users can just write Markdown or HTML and Retejo will figure this out automatically for you

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

8/

REMEMBER: this is for power-users, not regular users

How would you get ActivityPub / ActivityStreams into HTML using RDFa‽

Like this:

<div vocab="https://www.w3.org/ns/activitystreams#" typeof="Note">
<p property="name">Hello!</p>
<p>How do you do?</p>
</div>

AGAIN, REMEMBER: this is for power-users, not regular users.

Regular users can just write Markdown or HTML and Retejo will figure this out automatically for you

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

7/

If you are wondering what RDFa is —

You might be more familiar with OpenGraph.

https://ogp.me/

OpenGraph is usually the thing that causes "preview cards" to be showed for links shared on social-media.

OpenGraph is written in RDFa. Which, in practice, is some special HTML elements added to the page.

For example:

<meta property="og:image" content="https://example.com/img/preview.png" />

So what about ActivityPub‽ —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

7/

If you are wondering what RDFa is —

You might be more familiar with OpenGraph.

https://ogp.me/

OpenGraph is usually the thing that causes "preview cards" to be showed for links shared on social-media.

OpenGraph is written in RDFa. Which, in practice, is some special HTML elements added to the page.

For example:

<meta property="og:image" content="https://example.com/img/preview.png" />

So what about ActivityPub‽ —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

6/

Obviously, beginners are NOT going to do this, but — some power-users may want this level of control.

There are different way this could be done, but — one way might be that power-users could use RDFa to explicitly specify what data from the HTML gets into the ActivityPub / ActivityStreams data.

Again, beginners and typical users would NOT do this.

But a power-user might want to.

Here is an example —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

6/

Obviously, beginners are NOT going to do this, but — some power-users may want this level of control.

There are different way this could be done, but — one way might be that power-users could use RDFa to explicitly specify what data from the HTML gets into the ActivityPub / ActivityStreams data.

Again, beginners and typical users would NOT do this.

But a power-user might want to.

Here is an example —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

5/

So, what would be a good user-experience (UX) for power-users be — in a system that automatically creates ActivityPub / ActivityStreams data from HTML and Markdown‽

One thought I had is that power-users could explicitly mark what data from their HTML gets into the ActivityPub / ActivityStreams data (if they want to).

I'll explain —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

5/

So, what would be a good user-experience (UX) for power-users be — in a system that automatically creates ActivityPub / ActivityStreams data from HTML and Markdown‽

One thought I had is that power-users could explicitly mark what data from their HTML gets into the ActivityPub / ActivityStreams data (if they want to).

I'll explain —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

4/

I think one mistake some software does is — they create a good experience for beginners, but have a poor experience for power-users.

And keep in mind that — some beginners become power-users later on.

I think it is important to design for power-users, too, in addition to beginners.

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

4/

I think one mistake some software does is — they create a good experience for beginners, but have a poor experience for power-users.

And keep in mind that — some beginners become power-users later on.

I think it is important to design for power-users, too, in addition to beginners.

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

3/

If a typical user is writing in Markdown, and their Markdown file has a level-1 heading right at the beginning, then —

That could go into the ActivityPub "name" field.

And, similar could be done for HTML, too.

...

But what about power users —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

3/

If a typical user is writing in Markdown, and their Markdown file has a level-1 heading right at the beginning, then —

That could go into the ActivityPub "name" field.

And, similar could be done for HTML, too.

...

But what about power users —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

2/

What are "good" ways of automatically creating ActivityPub / ActivityStreams data from HTML and Markdown‽

I think the answer depends on who, for example, is writing HTML, and how they are writing it.

For example, is this a typical user? Is this a power-user? Do they know HTML? And if they do know HTML, how well do they know it? Etc?

I will show you what I mean —

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

2/

What are "good" ways of automatically creating ActivityPub / ActivityStreams data from HTML and Markdown‽

I think the answer depends on who, for example, is writing HTML, and how they are writing it.

For example, is this a typical user? Is this a power-user? Do they know HTML? And if they do know HTML, how well do they know it? Etc?

I will show you what I mean —

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

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

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

@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.

@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.

@Seirdy

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

@Seirdy

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

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

@AAD_OeAW @ACDHCH_OeAW @w3c

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.

...

@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...

📣 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.

#blog #RustLang #html #css #SemanticHTML #rss #rdfa

📣 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.

#blog #RustLang #html #css #SemanticHTML #rss #rdfa

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, the what namespace should I add for the `fediverse:` prefix to point to?

Which one is true for this feature, @MastodonEngineering?

@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 😅

@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

The latest edition of the annual Web Data Commons report is out!

This report tracks the growth of #Web accessible structured data embedded in #HTML documents.

Benefits?

HTML docs are opening up a new and important data access frontier for user-agents, query tools, and query languages (#SQL, #SPARQL, #GraphQL) that ultimately aid both enterprise and individual agility.

http://webdatacommons.org/structureddata/2022-12/stats/stats.html

#RDF #RDFa #JSONLD #Microdata #Microformats #StructuredData #SemanticWeb #Web30 #SchemaOrg

@fedilink,

Great to see that you make good use of #RDFa, #RSS, and #Atom re open #DataAccess and #DataConnectivity.

Courtesy of the @openlink Structured Data Sniffer Browser Extension (@datasniff) [1], I am able to see all the cool structured data embedded in your #HTML docs.

[1] https://medium.com/openlink-software-blog/openlink-structured-data-sniffer-osds-version-2-21-6-4026eddb47db -- About the OpenLink Structured Data Sniffer (#OSDS) Browser Extension

/cc @Mastodon

#Fediverse #LinkedData #OpenWeb

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/