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

Namespace of draft SSP metaschema #351

Closed
wendellpiez opened this issue May 15, 2019 · 3 comments
Closed

Namespace of draft SSP metaschema #351

wendellpiez opened this issue May 15, 2019 · 3 comments
Assignees
Labels
Scope: Modeling Issues targeted at development of OSCAL formats User Story

Comments

@wendellpiez
Copy link
Contributor

User Story:

As a user of the draft (FedRAMP-oriented) SSP metaschema, I need to know what is its namespace and (by implication) its governing authority. Its current namespace, urn:OSCAL-SSP-metaschema is a placeholder and has not (TMK) been vetted by anyone.

Goals:

XML namespaces commonly indicate the governing authority for a family of documents (probably sharing a schema). For example, the Catalog and Profile layers now have namespace "http://csrc.nist.gov/ns/oscal/1.0". (See #306 for more.)

It would be good if the SSP metaschema had a namespace conforming to this (implicit) requirement.

Dependencies:

See file https://github.com/usnistgov/OSCAL/blob/master/schema/metaschema/oscal-ssp-metaschema.xml to confirm the present state of the namespace assignment in this schema.

But note also this Issue is not only about namespaces but also by implication about how to attribute 'ownership' or 'maintainership' of these metaschemas and schemas, especially when they are in draft.

Acceptance Criteria

We need a decision on namespace policy (at least short-medium term) and what to do in this case, keeping in mind that we need stable namespaces with no complex contingencies.

Depending on the decision we need Issues for follow-on work such as deploying a "real" namespace identifier for the draft SSP schema; modifying XML to conform to it; documenting namespace policy (possibly as part of Metaschema documentation work).

@david-waltermire
Copy link
Contributor

We discussed this on 8/15/2019 and the decision was to use the same namespace as the lower (catalog and profile) models. i.e. http://csrc.nist.gov/ns/oscal/1.0.

@david-waltermire
Copy link
Contributor

This will be closed once PR #464 is pulled.

@david-waltermire
Copy link
Contributor

This has been completed in PR #464.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Modeling Issues targeted at development of OSCAL formats User Story
Projects
None yet
Development

No branches or pull requests

3 participants