Gary, I'm also sorry I missed the Dec 16 call.
I was confused by the phrase "two sources of truth" since 1) if there is a conflict between two versions of "truth" then at least one of them MUST be wrong, and 2) Markdown is a markup language for prose, not a modeling language. But you clarified that: On the call we identified 2 areas/requirements: > > - Validate the Markdown as part of the spec CI/CD process (e.g. a > Github action in the spec repo) > > > - Import the Markdown information into OWL automatically > > - Developing a specification for the model represented in Markdown and defining the algorithm for validating it means that Markdown is being used as just a file format, not a modeling language. JADN models can be saved in Markdown format, but most Markdown documents are not valid information models. Plus if the portion of the model specified in Markdown is imported into OWL, then after importation the merged OWL specification becomes the single source of truth. That's all good. I look forward to working with the group on model definition, validation/translation requirements, and tooling. Regards, Dave On Wed, Dec 16, 2020 at 1:57 PM Gary O'Neall <[email protected]> wrote: > Hi Rishabh, > > > > We can definitely use your help on the tooling side. > > > > On the call, we decided to use both Markdown and OWL as 2 “sources of > truth”. For the Markdown, we will specify a set of constraints and > requirements to the format that will allow tools to use the information in > the OWL document and possibly other schema formats. > > > > We discussed JADN would be a good future direction, didn’t have enough > adoption and tooling to use today. > > > > There is a lot of opportunity to add tooling to reduce the manual labor > and to produce the spec. > > > > On the call we identified 2 areas/requirements: > > - Validate the Markdown as part of the spec CI/CD process (e.g. a > Github action in the spec repo) > - Import the Markdown information into OWL automatically > > > > I plan on starting a Google doc the tech team can collaborate on to > document the workflow and specify the Markdown constraints. > > > > We’ll probably touch on this topic in our next Tech call which will be > January 5. > > > > Thanks, > > Gary > > > > > > > > *From:* [email protected] <[email protected]> *On Behalf Of > *Rishabh Bhatnagar > *Sent:* Wednesday, December 16, 2020 8:58 AM > *To:* [email protected] > *Subject:* [spdx-tech] Tech - Team meet 16th Dec 2020 > > > > I'm sorry I couldn't make it to the last tech-team meet (as I had a long > day and it was very late in India). > > > > I've something to add. > > 1. If we are opting for JADN, even I can help along with David Kemp sir. > > 2. If we need to develop something ourselves for the "unified source of > truth", I would love to contribute and would put my best foot forward for > it. > > > > One question: What is ISO all about? How does it affect our choice of > format for the "unified source of truth"? [kindly excuse my ignorance]. > > > > > > Thanks & Regards, > > Rishabh Bhatnagar > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3951): https://lists.spdx.org/g/Spdx-tech/message/3951 Mute This Topic: https://lists.spdx.org/mt/79005495/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
