The mission of this community group is to establish a draft standard for a RDF-based representation of the HTML-vocabulary. With the HTML-vocabulary in RDF, any type of an HTML-document can be meaningfully represented, generated and validated using nothing but standard semantic technologies, without any vendor lock-in. In addition, full provenance can be provided for a generated HTML-document, as every atom of the document can be described and semantically enriched, ex ante (RDF) and ex post (Rdfa). For instance, the originating algorithm that calculates a certain budget amount in a governmental HTML-document can be linked to the table cell containing the very value. HTML-documents have a wide variety of use and so has the HTML vocabulary. The HTML-vocabulary can be used to generate 100% correct HTML or xHTML and to validate this. The HTML vocabulary can be used to model the front end of a website or application, whereas the logic behind the front end can be captured in SHACL Advanced Features, making for a full semantic representation and execution of digital infrastructure, without any vendor lock-in. An HTML-document can be generated with full compliance to laws and regulations, as these norms can be linked and applied while using the HTML-vocabulary. With full provenance, an HTML-document can battle fake news and show realtime how certain sensitive data in the document (privacy, security) was derived.
The community group will come up with a 0.1 draft specification. This will be input for a future working group within W3C. The community group can make use of the currently available draft specification as developed by the Dutch Ministry of Finance in a working prototype for the Dutch governmental budget cycle. By starting this community group, the Dutch Ministry wants to contribute to an open source based digital infrastructure.
Group's public email, repo and wiki activity over time
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Welcome to the third session for the semantic HTML-vocabulary community group! It has been a long time but not without interesting developments. Looking forward to be able to share these with you. We are also going to ask you to get involved by simply using the vocabulary and related tooling, and sharing your experiences with us. Eternal glory upon those that have done so before this meeting 😉
1. Opening of the meeting 2. Welcome by the chair 3. Introduction of new members 4. Housekeeping (secretary/notes) 5. Recent developments * Tooling (RDF2HTML and HTML2RDF) * HTML vocabulary in use at the Dutch Ministry of Finance * Updated vocabulary (html attributes, logic, labeling, general hygiene) * OntoReSpec, OntoManchester, OntoMermaid 6. Your experience in using the vocabulary and tooling 7. Draft report for the community group 8. Planning/roadmap 9. Questions and suggestions 10. Closing of the meeting
The past year has gone by without any news…despite there being many developments. My apologies for that! This was mainly due to all the developments that took all my time. In the github you will find the latests commits, including new tools like RDF2HTML and HTML2RDF. The first offers the possibility to serialize a RDF model of an HTML document into HTML and the latter gives you the possibility to parse any HTML document and express that in RDF.
Second, the HTML vocabulary has now been officially used in the budget tables for the Ministry of Finance of the Netherlands, as of the 19th of September 2023, when the tables were presented to the parliament of the Netherlands. That is some start of a vocabulary!
Third, the model has been updated. Mostly with metadata, with an exceptional small adjustment in the logic here and there, as we had to find a way to work around some bugs in PyShacl and Rdflib, without hurting our standard vocabulary too much. It now works with those tools as well. Although this has to be tested and improved much more…here lies a task for you guys 🙂 In addition, I still want to add some standard html attributes based on the Living Standard (already added many though!), rename (skos:prefLabel) the defined HTML elements without the pesky ‘<‘ and ‘>’ tags as that leads too much with unintended html rendering in other applications when dealing with our vocabulary and do some general hygiene in layout and labeling.
Fourth, this year saw the birth of an early version of OntoReSpec, the ontology specification generator according to the ReSpec standard. You can offer your ontology and then the tool creates a HTML document in which your ontology is nicely presented. OntoReSpec is based on the semantic HTML vocabulary. It is the second use case for our semantic HTML vocabulary. No more need for laborious documentation writing by hand to describe your ontology, instead let it generate documentation based on the ontology itself. OntoReSpec is still in development as of now.
Fifth, related to OntoReSpec I also had to come up with a Manchester Syntax repository in order to represent OWL ontologies in an accessible language instead of very technical OWL terms. This can be used to explain your model in more simple terms.
And last but not least, also related to OntoReSpec, there is the Mermaid repository to express OWL ontologies into the Mermaid diagram language. Feel free to play around.
The mission of this community group is to establish a draft standard for a RDF-based representation of the HTML-vocabulary. With the HTML-vocabulary in RDF, any type of an HTML-document can be meaningfully represented, generated and validated using nothing but standard semantic technologies, without any vendor lock-in. In addition, full provenance can be provided for a generated HTML-document, as every atom of the document can be described and semantically enriched, ex ante (RDF) and ex post (Rdfa). For instance, the originating algorithm that calculates a certain budget amount in a governmental HTML-document can be linked to the table cell containing the very value. HTML-documents have a wide variety of use and so has the HTML vocabulary. The HTML-vocabulary can be used to generate 100% correct HTML or xHTML and to validate this. The HTML vocabulary can be used to model the front end of a website or application, whereas the logic behind the front end can be captured in SHACL Advanced Features, making for a full semantic representation and execution of digital infrastructure, without any vendor lock-in. An HTML-document can be generated with full compliance to laws and regulations, as these norms can be linked and applied while using the HTML-vocabulary. With full provenance, an HTML-document can battle fake news and show realtime how certain sensitive data in the document (privacy, security) was derived.
The community group will come up with a 0.1 draft specification. This will be input for a future working group within W3C. The community group can make use of the currently available draft specification as developed by the Dutch Ministry of Finance in a working prototype for the Dutch governmental budget cycle. By starting this community group, the Dutch Ministry wants to contribute to an open source based digital infrastructure.
This is a community initiative. This group was originally proposed on 2022-06-03 by Flores Bakker. The following people supported its creation: Flores Bakker, Gregg Kellogg, Paola Di Maio, Wouter Beek, Ruben Taelman. W3C’s hosting of this group does not imply endorsement of the activities.
floresbakker/htmlvoc
