iherman
commented
7 months ago @msporny, you assigned me to this issue, but I would prefer you do the changes, because changing actions is a sensitive area, and I am not sure to have the right experience. I have compared the repo with the data integrity repository, and I see two differences that, most probably, make account for the problem. These are:
- In the
settings/Pagesthedi-data-integrityrepo says that the source of the build & deployment are github actions. I would think the same should be used in the current repo, which is not the case (it says to deploy from a branch). I presume that, under the current settings, thegh-pages.ymlaction has no effect. (It is, otherwise an almost carbon copy of the action fordi-data-integrityaction, except for the path to the vocabulary files.) - The
di-data-integrityrepo has a separate action calledlint-vocab.yml, which is used to check the vocabulary. I would think that should be copied here with the obvious change ofvocab/security/➝vocab/in the path of the command in the last line.
Would you do these changes if you agree with them?
Also: once this is done, we also have to set up an alias for https://www.w3.org/ns/credentials/status to point to the vocabulary. I hope that will happen without problems as it is, although it may be easier to do it with https://www.w3.org/ns/credentials/status/...
msporny
On the data model and DI repositories it is possible to see the generated vocabulary file via, say,
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html
This is done via some github action magic. The same should be done in this repository to see the generated voabulary file via
https://w3c.github.io/vc-bitstring-status-list/vocab/vocabulary.html