-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alignment with ReSpec's in-browser architecture with JS #2
Comments
This would indeed improve the feeback loop in local development, when working with html based respec configurations. Working in markdown (which many do) would still require an additional step. We could explore both avenues. What do you think @architolk @Bakkej? |
We could look into this more. We did look at using javascript libraries instead and the suggestion does seem to align with one of the possible solutions suggested by @architolk; Using a Javascript library to generate the html-representations on the fly, possibly using some API to fetch the rdf-resources. |
Agreed, the repo name then suggest a transformation to ReSpec. rdf2md would be a better fit? |
We decided on rdf-template. See https://github.com/pldn/rdf-template |
In light of this discussion we created the repository rdf-template. This repository can be used to develop a JS library that fits within the respec architecture as described above. |
@RiX012 pointed me to this excellent idea. I however think that the current architecture may not be compatible with the ReSpec architecture. ReSpec uses in-browser JavaScript modules that compose into the DOM.
The stated pre-compilation step, configuration, etc. imho does not align with that. Suggestions:
That would improve the feedback loop when writing ReSpecs with a local webserver, as there is no need for a render/compilation step that goes either through local Java or remote GitHub Actions.
Cf. OpenAPI plugin for ReSpechttps://lists.w3.org/Archives/Public/spec-prod/2022AprJun/0007.html
cf. SPARQL templating with Snowman https://github.com/glaciers-in-archives/snowman
The text was updated successfully, but these errors were encountered: