Skip to content
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

In the schema map, attributes are not linked to parent #549

Closed
bradh opened this issue Nov 30, 2019 · 5 comments
Closed

In the schema map, attributes are not linked to parent #549

bradh opened this issue Nov 30, 2019 · 5 comments
Labels
bug Scope: Tooling and APIs Issues targeted at development of tooling and APIs to support OSCAL content creation and use. Scope: Website Issues targeted at the OSCAL project website.
Projects

Comments

@bradh
Copy link
Contributor

bradh commented Nov 30, 2019

Describe the bug

See https://pages.nist.gov/OSCAL/documentation/schema/catalog/xml-schema/#oscal-catalog-xml_name for an example - note the This attribute appears on: . part. That should provide the list of elements that the attribute applies to.

Who is the bug affecting?

Users of the schema map.

What is affected by this bug?

Documentation / situational understanding.

When does this occur?

Always.

How do we replicate the issue?

See above.

Expected behavior (i.e. solution)

Attributes in the docs pages include the parent element, ideally "hot-linked".

Other Comments

Relatively low priority - by the time you're looking at an attribute, you've probably already found the relevant parent.

@bradh bradh added the bug label Nov 30, 2019
@wendellpiez
Copy link
Contributor

This was working in the past. A repair will probably follow easily on a diagnosis of why it is happening now.

@bradh
Copy link
Contributor Author

bradh commented Dec 7, 2019

I backed out 84fc962 and that gave me back the links. However it obviously results in duplicate entries.

@wendellpiez
Copy link
Contributor

Thanks @bradh for sniffing this out it will be helpful.

@wendellpiez
Copy link
Contributor

So #560 is the PR to correct this.

@david-waltermire david-waltermire added Scope: Tooling and APIs Issues targeted at development of tooling and APIs to support OSCAL content creation and use. Scope: Website Issues targeted at the OSCAL project website. labels Jan 9, 2020
@david-waltermire david-waltermire added this to To do in Sprint 26 via automation Jan 9, 2020
@david-waltermire
Copy link
Contributor

The fix for this has been merged and verified. Closing.

Sprint 26 automation moved this from To do to Done Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Scope: Tooling and APIs Issues targeted at development of tooling and APIs to support OSCAL content creation and use. Scope: Website Issues targeted at the OSCAL project website.
Projects
No open projects
Sprint 26
  
Done
Development

No branches or pull requests

3 participants