Conal Tuohy

I second @VladimirAlexiev's "awesome" proposal. Here's more information about "awesome" lists. https://github.com/sindresorhus/awesome

Needs to play nicely with ETags and other HTTP caching mechanisms.

A bit of refactoring might be helpful first to separate the differently named APIs into separate Java source code files, so that the differences between the javax and jakarta branches...

I think XHTML5 compatibility is still worth having. Note that at least _some_ of the problems I originally had with embedding UV in an XHTML page were due to errors...

@timathom mentioned xphoneforms as an alternative to this repo. At the moment I am working directly on the xsltforms.js file, but at some stage I'd like to contribute my work...

Thanks Alain! May I suggest you update the README files of the other repositories to mention that they are obsolete, and to refer instead to xphoneforms?

Thanks Alain! For me, the value of the xmlns is in clarity of processing mixed-namespace markup server side, and in being able to reuse stylesheets I already have which target...

To reiterate my comment on Twitter: I'd recommend an approach where you dump all your JSON-LD graphs into a SPARQL graph store, and then write some SPARQL CONSTRUCT queries to...

A SPARQL graph store is an extra component, and obviously that is automatically a cost that counts against it (though e.g. deploying fuseki.war is not terribly involved). To me the...

@rsimon the OC data is already expressed in RDF using JSON-LD; that's in fact what prompted my suggestion of SPARQL as the transformation language. But I do agree it's a...