Comments (11)
While looking and trying to understand this one, I found non-working data-type #-anchored references from both Outline and Reference Pages - should I fix that one first? It does looks ugly and very broken, while this one seems more obscure.
Though it seems that there is no issue created for it yet.
from oscal-reference.
I am not 100% certain this belongs in OSCAL-Reference. If this does require a fix in usnistgov/metaschema-xslt, I will 1) request the assigned developer open a cross-referencing issue in that repo and 2) work with me or the delegated developer to coordinate a potential fix to that repo.
from oscal-reference.
@JustKuzya, I heard you were looking into picking this one up. If you are able and willing, please do!
from oscal-reference.
While looking and trying to understand this one, I found non-working data-type #-anchored references from both Outline and Reference Pages - should I fix that one first? It does looks ugly and very broken, while this one seems more obscure.
Though it seems that there is no issue created for it yet.
@aj-stein-nist volunteered to open an issue for this as reported by Dmitry.
from oscal-reference.
@JustKuzya and @wendellpiez and @aj-stein-nist have volunteered to sync on this and complete a root cause analysis, confirm whether this is a minor document generation issue or something more significant, and act accordingly.
from oscal-reference.
I set aside some time with @JustKuzya and @wendellpiez tomorrow as today as pretty packed for me.
from oscal-reference.
We need to enumerate all constraint
s with allowed-values
for props of a given name
. There is some homework for Dmitry and I to do here and I will want to consult @david-waltermire-nist and the Metaschema core team before moving forward on adapting the documentation further. Moving this to blocked in the interim.
from oscal-reference.
A path to find all these is unfortunately not straightforward since the @target
uses XPath syntax, and XPath can't (yet) parse XPath ... but a couple of greedier queries could work. //allowed-values[not(@allow-other='yes')]
could be a start.
Keep in mind that allowed-values targeting prop
could either indicate prop
in their @target
, or it could be implicit (by virtue of targeting "." in the definition of a prop).
Also, this Issue implicates not only allowed values on props, but also others....
from oscal-reference.
I just wanted to give a status update: we are working on usnistgov/metaschema#411 but it will not get completely reviewed and possibly merged by the end of this sprint, but work continues.
from oscal-reference.
There will be updates to the aforementioned issue but as of a sync with Metaschema developers I am working with on the associated PR for issue 411, more work is needed to be done on the spec and updating documentation will have to wait on certain discuss of allowed values processing that ought to come after the next two weeks of sprint, so I will be moving this out of Sprint 75 for now.
from oscal-reference.
This is not a bug in the allowed values. It is a bug in marking not showing up properly in the documentation. See usnistgov/OSCAL#1972
from oscal-reference.
Related Issues (15)
- Support for local development HOT 6
- Overlapping elements in outline pages of generated model reference HOT 3
- Replace OSCAL data type pages with links to Metaschema datatypes HOT 4
- Include OSCAL processing specifications HOT 1
- Options needed for publishing draft/experiment work as a part of DEFINE HOT 4
- Set up meta redirects linking users to release artifacts
- Add notice of experimental prerelease models HOT 1
- [Dummy Issue] Testing Issue Triage
- Release assets redirect missing from generated pages site
- Last update date in footer of model-specific documentation is not set. HOT 3
- Correct schema and model links
- Set up linkchecking HOT 3
- OSCAL-Reference needs a nice landing page. HOT 7
- Model reference pages failing to link between each other HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from oscal-reference.