{"id":12,"date":"2024-10-21T18:00:39","date_gmt":"2024-10-21T18:00:39","guid":{"rendered":"https:\/\/www.w3.org\/community\/htmlvoc\/?p=12"},"modified":"2024-10-21T18:00:39","modified_gmt":"2024-10-21T18:00:39","slug":"update-on-html-vocabulary-draft-report","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/htmlvoc\/2024\/10\/21\/update-on-html-vocabulary-draft-report\/","title":{"rendered":"Update on HTML vocabulary: draft report"},"content":{"rendered":"\n

Hi all!

Exciting news on our end: a first version of a draft report for the community group regarding the HTML vocabulary is available now through the Github<\/a>. This specifies the HTML vocabulary in a readable format, using the ReSpec standard. Here one can see a preview of the draft report for the W3C community group:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this document, one can read the specification of classes, properties, shapes and the like to get an understanding of the HTML vocabulary.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The document was actually generated using OntoReSpec<\/a>, an open source tool based on semantic web technology. Here comes the twist: OntoReSpec uses the HTML vocabulary to generate the very HTML document we are looking at. The HTML vocabulary proves that it works by generating its own specification.

The HTML vocabulary has changed somewhat since the last time we sent out an update. Not so much a change of course, but more of a finetuning to align as much as possible with the Living Standard of HTML itself.

Consider for example the algorithm to serialize HTML fragments, modeled through the SHACL node shape shp:HTMLFragmentSerializationAlgorithm<\/em>. This is the engine of the vocabulary that does all the work.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It now calls several SPARQL functions in order to serialize a HTML document from its leaf nodes up and till the root element and the document containing it. We thus could remove four unnecessary node shapes and improve the efficiency and readability of the vocabulary. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The current version of the HTML vocabulary will now undergo acceptance testing within the Dutch Ministry of Finance; in addition, it has already been proven to work in an OntoReSpec implementation as is mentioned above. <\/p>\n\n\n\n

The concepts and methodology behind the HTML vocabulary, basically a form of an abstract syntax tree, are generic and can be applied outside the HTML domain. We came up with an XML vocabulary<\/a>, with which XML dialects can be modeled. See for instance draft versions of OntoSVG<\/a> and OntoArchimate<\/a>. Going even further, we can now also apply this to domains such as English<\/a>, Python<\/a> and SPARQL<\/a> itself. These are for now just inspiring attempts but can be developed more seriously in the future, just like we did with the HTML vocabulary.

Are we done yet with the HTML vocabulary? No. There are still some issues, although minor ones. We still want to finetune the documentation, enriching some definitions, perhaps improving OntoReSpec on the way as well. The ReSpec document contains two oddities at this moment: (1) unnecessary warning of 10 duplicate definitions,<\/em> caused by classes and properties that are identically written but for an upper case letter. Think of html:abbr (property) versus html:Abbr (class). ReSpec does not like this. I have raised an issue at the Github for ReSpec as I do not know how to handle this in ReSpec. (2) the “Latest editor’s draft:<\/em>” link in the document refers to a non-existing Github page, of which I do not know its origin. I have added this to another issue at the Github of ReSpec. Finally, and most importantly, we wish to add a rudimentary validation model of the structure of an HTML document.

All in all it looks like we are going to deliver our community group draft report by the end of the year. We can organize a meeting around that time and see what we as a group still want to do with the specification and how and when we can move forward to a formal working group trajectory.<\/p>\n\n\n\n

We’ll keep you updated. In the mean time, feel free to read the specification, both the HTML document and the turtle file, and let us know what you think. Are you satisfied with the current state of the HTML vocabulary? Do you have specific wishes to improve the ReSpec documentation? Critical complaints and constructive criticisms are welcome, just as well as charming compliments \ud83d\ude42<\/p>\n\n\n\n

Kind regards,<\/p>\n\n\n\n

Flores Bakker
Chair of the HTML vocabulary community group
Enterprise Architect @ Dutch Ministry of Finance<\/em><\/p>\n\n\n\n

Wouter Beek
Co-founder @ Triply<\/em><\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi all! Exciting news on our end: a first version of a draft report for the community group regarding the HTML vocabulary is available now through the Github. This specifies the HTML vocabulary in a readable format, using the ReSpec … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":21511,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"","footnotes":""},"categories":[1],"tags":[6,3,7,5],"class_list":["post-12","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-draft","tag-html","tag-rdf","tag-report"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/posts\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/users\/21511"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":16,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/posts\/12\/revisions"}],"predecessor-version":[{"id":32,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/posts\/12\/revisions\/32"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/categories?post=12"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/htmlvoc\/wp-json\/wp\/v2\/tags?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}