You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Evaluate the feasibility of a standalone OSCAL component editor (as supported by the component-description model) using CSX (client-side XSLT) in SaxonJS.
SaxonJS event handling could support UI features. There could be local load and save as demonstrated in other CSX applications. It could even embed a format converter to make it possible to read and write JSON not just XML. (Or not.)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Evaluate the feasibility of a standalone OSCAL component editor (as supported by the
component-description
model) using CSX (client-side XSLT) in SaxonJS.SaxonJS event handling could support UI features. There could be local load and save as demonstrated in other CSX applications. It could even embed a format converter to make it possible to read and write JSON not just XML. (Or not.)
The text was updated successfully, but these errors were encountered: