Closed
Conversation
Allows to refer to the XSL from outside this github repo.
Now we have a nice display of the XEP number, yay!
The idea would be to integrate this in the XSF XEP XSLT. However, it doesn't work that well: - xinclude does not work in browser XSLT engines.
Syntax and indentation
This schema’s canonical URL is https://linkmauve.fr/ns/xmpp-doap but it is also hosted here for ease of contribution.
For each implemented XEP, this: * adds a column with the title of the XEP, * the XEP abstract is injected in the "title" attribute; * adds a column with the latest revision number, * the date of the latest revision is injected in the "title" attribute; * adds a "title" attribute to the implemented revision number with the publication date of that version; and * styles the implemented revision column according to whether the project implements a current or outdated revision. It does this by referencing the relevant XEP XMLs, not the abridged list found at https://xmpp.org/extensions/xeplist.xml as that one does not have full revision details (so we can extract the date of the *implemented*, as opposed to latest, revision) and it also makes matching marginally more awkward as the XEP numbers are given with a varying number of digits. Lastly, that relies on xeplist.xml being complete and up to date whereas taking the XEP references entered by the user relies on the *.html and *.xml versions being in the same path. One marginal advantage is that this doesn't break if the author announces support for private XMLs (which probably won't be in xmpp.org or in xeplist.xml). Note 1: Generation with xsltproc will probably not work: https://gitlab.gnome.org/GNOME/libxslt/-/issues/28 Use a better tool instead, such as Saxon (http://saxon.sourceforge.net/). Note 2: If the XEP XMLs were served with `Access-Control-Allow-Origin: *`, the XML could be served directly and the browser would apply the XSLT transformation itself.
- Use xeplist.xml instead of querying each XEP for name and version - Show XEP number and name in the same column - Show version and latest version in the same column - Show only a Green Checkmark (TM) if the version is up to date - Show a yellow badge with the latest version otherwise
* improve alignment of table elements * show latest version only if it differs from implemented version * add colors for remaining XEP status elements * use color variables
Otherwise it kinds of misses the point of having astylesheet...
In discussion with past contributors...
bkmgit
force-pushed
the
linkcheck
branch
2 times, most recently
from
81a64c3 to
7d80372
Compare
Contributor
Author
|
Closing in favor of #159 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on top of #154
Closes #148