Re: Collaboration on the specs

Hi Enrico, hi all,

I don't have a hard preference for hypothes.is as I have not used it before. I don't have any objections to just using git issues for this as it allows to frame problems better (maybe a comment is not worth making if you don't want to bother creating an issue/pr for it?).
At the same time, it's true that a tool such as hypothes.is brings a bit of the productivity of MS word collaboration inside of an opensource development. I could help with setting up a pipeline that publishes to a dedicated page to where it can be referenced statically by hypothes.is.

In any case, I do have a strong preference to using markdown as opposed to the current html approach 🙂. Besides separation of concern (styling vs content), It also makes referencing a line in an issue easier:
[cid:61f1950f-c54e-413d-be76-0fdc4f38452b]


Best regards,



Mathias Vanden Auweele

+32 491 16 16 88

https://matdata.eu


http://www.linkedin.com/in/mathiasvda





________________________________
From: Enrico.Daga <enrico.daga@open.ac.uk>
Sent: Tuesday, March 31, 2026 10:59
To: public-facade-x@w3.org <public-facade-x@w3.org>
Subject: Collaboration on the specs

Hi all,

As discussed, I rearranged the specs in a single repository [1]. However, the annotations on hypothesis.io are now orphans (the page no longer exists). I moved some of the comments to issues, but this may be a problem moving forward. I discussed this in [2], but I wanted to have a general discussion on this aspect here.

I see three options (but feel free to propose others):


  1.
We stick to GitHub and Emails only for discussion (small comments can be made on GitHub files using the add comment on commits function)
  2.
We keep hypothesis.io assuming there will be no changes to the URLs of the specs from now on
  3.
We move the content of the specs to Markdown and develop a simple build system to generate the HTML versions — the idea is that we can comment on the Markdown using GitHub comments and that it is easier than doing the same on HTML.

WDYT?

Best,

Enrico

[1] https://github.com/w3c-facade-x/facade-x-specs

[2] https://github.com/w3c-facade-x/facade-x-specs/issues/4



--
Enrico Daga, PhD
Senior Research Fellow
Knowledge Media Institute
The Open University
http://enridaga.net

http://sparql-anything.cc