Open bwbohl opened 3 years ago
I think that 2. would be very problematic. Not breaking validation was the reason to have the schema repository
So here should be an index.html
here that looks something like this:
<head>
<meta http-equiv="Refresh" content="0;url=https://music-encoding.org/resources/schemas.html">
</head>
<body>
</body>
How do we integrate it into the CI?
As I was instead thinking the other way round, I created a test deployment in my fork. I copied the contents of schemas.html and added some dynamic to automatically list the contents of the respective version folders in a Jekyll/GitHub page. It still needs the proper MEI styling, and maybe using https://github.com/jayanta525/github-pages-directory-listing could even improve its appearance. But as a dummy test, it’s OK: https://bwbohl.github.io/schema/
https://music-encoding.org/resources/schemas.html
is ok as first entry point although it could bear some more info on the schemata and it lacks links to older versions.https://music-encoding.org/schema/
on the other hand is a pretty ugly website that bears almost no contents, except for the short readme of this repository. I see two options here:https://music-encoding.org/resources/schemas.html
tohttps://music-encoding.org/schema/
and prettify what's found herehttps://music-encoding.org/resources/schemas.html
While 2. might be easier to integrate with the website look and feel it would probably destroy the possibility to access the schemata directly for validation, e.g. by calling
https://music-encoding.org/schema/4.0.1/mei-all.rng
(and I like this ;-)Opinions?