In the hypertext architecture, when making a reference, such as a hypertext link, we don't just refer to an information resource. Well, we can, but we can also refer to a particular part of or view of a resource. The string which, within the document, defines the other end of the link has two parts. It has the identifier of the document as a whole, and then optionally it has a hash sign "#" and a string representing the view of the object required.

Note of Tim Berners-Lee

Even if this standard is not used for years, some ideas are interesting. How and which data is collected and used are pretty well standardized.

It can somehow interact with the GDPR.

It will solves a lot of tooltip or popover issues

Similar to microdata.

Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviors and usage patterns. - https://microformats.org/wiki/about

What is the difference between microformats and microdata? It seems that microdata is an extension of microformats. Also microdata is meant for HTML5, whereas microformats is meant for everything.

How to make design tokens interoperable? With a format that describes their serialization and which metadata should be attached to it.

Different loading hints:

• async resource is loaded when the browser can
• defer resource is loaded when the DOM is parsed (less priority than async)
• rel=preload load the resource before the parsing and everything else
• fetchpriority with value high, low and auto. They are hints.
• rel=preconnect indicates that a connexion has to be established ASAP.
• rel=dns-prefetch resolves the domain name without fetching the resource.
• loading attribute determine when an image is loaded depending of its value:
  • eager: the image is loaded immediately
  • lazy: the loading is delayed until the user scroll to it.

From Tim Berners-Lee
Date: 1998, last change: 2013-03-04 22:56:21

When you design a system or a language, if the features can be broken into relatively loosely bound groups of relatively closely bound features, then that division is a good thing to be part of the design. This is just good engineering. It means that when you want to change the system, you can with luck in the future change only one part, which will only require you to understand (and test) that part. This will allow other people to independently change other parts at the same time. This is just classic good software design and books have been written about it. The corollary, the TOII is less frequently met.

This kind of “insert block” user interface concept is showing up in almost every blogging tool, web editor, note-taking app, and content management system. People like it and it makes sense.

Embed blocks accross the web with the future block protocol :D

If APIs can share data between programs and websites, then I understand the block protocol as a way to share UI components and logic between websites.

Latest standard of the year 2022