Skip to content

[ENHANCEMENT] technique for variant modeling #5

Description

@StevenJenkinsJPL

I've always thought that OWL named graphs are a good mechanism for modeling variants. In the simplest case, create one description for common assertions and one for each variant. Then there are two scopes for reporting and analysis: common plus variant 1, common plus variant 2. This extends to nested subvariants and arbitary combinations of variants, e.g., space optical plus ground optical, space RF plus ground RF, excluding optical/RF combinations.

I think we have everything we need to do this now with the exception of specifying multiple variant description roots (i.e., bundles) in build.gradle and the nesting the resulting analysis products under the appropriate variant. This seems like a really clean way to go about it and doesn't require any new notation or vocabulary for variants per se.

I suppose we could make a separate branch in git for each variant but that seems almost impossible to manage.

It might be helpful for the UI to have a perspective for each description root and hide anything not transitively imported by it. Switching perspectives is just a click.

Thoughts?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions