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

Requirements editing needs to be simplified for editors #45

Open
ogcscotts opened this issue Jun 24, 2024 · 2 comments
Open

Requirements editing needs to be simplified for editors #45

ogcscotts opened this issue Jun 24, 2024 · 2 comments

Comments

@ogcscotts
Copy link
Contributor

The structure for authoring Requirements (and thus Conformance statements and classes for both) is complicated for editors. The DocTeam is requesting proposals for a more simple means to edit this information.

Please suggest the most intuitive way for editors to create this information.

Two end results are likely:

  1. Metanorma is updated to reflect the new content model; or
  2. A parsing tool must be developed to extract the Requirements information and create the Metanorma files.
@ghobona
Copy link
Contributor

ghobona commented Sep 9, 2024

Discussed 2024-09-09

@opoudjis is going to create a ticket, in the metanorma-ogc repo, outlining a proposed workflow.

@ogcscotts will invite OGC Members to provide feedback during the 130th OGC Member Meeting.

@opoudjis
Copy link

Proposal is in metanorma/metanorma-ogc#716

It is conditional on the implementation of metanorma/modspec-ruby#2, the integration of YAML into Metanorma via an object model (although the workaround via Liquid that we have already published will still work.)

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

No branches or pull requests

3 participants