Hi Sean,
Thanks for writing this up. I noticed that you made changes both to the content and the template in your draft. I thought that many of the template changes represent good improvements. After reading through Steve’s email and a brief glance at his PR, perhaps we could merge back some of your template changes for other profile authors to use. This may be a good discussion to have for the next tech call since it sounds like the template is blocking some progress on other profile definitions. In terms of the content, I thought the definitions had good precision and were technically descriptive. However, I have a couple high level consistent concerns mainly due to compatibility with previous versions of SPDX. I don’t see as much benefit to the re-wording or renaming relative to the migration costs we would incur. For example, I think we should continue to use the term “SPDX” when referencing the spec and not introduce a new term. There are also definitions for similar objects in the SPDX ontology (e.g.SpdxElement, SpdxItem, SpdxDocument). From the modeling discussions, it didn’t sound like these objects were significantly different, but the descriptions provided do not include any of the original language leaving me to wonder if we’re defining something totally different or if we’re just using different descriptions. The SPDX ontology includes more semantic information on what the classes represent – I think it would be useful to include those in the definitions. In either case, if someone is coming from SPDX and sees a totally different description, we should have a good reason and a mapping to communicate to the current SPDX adopters. Rather than go through and suggest specific changes for each of the descriptions and names, I though we should get aligned at a high level first. Gary From: [email protected] <[email protected]> On Behalf Of Sean Barnum Sent: Tuesday, March 23, 2021 8:45 AM To: [email protected] Subject: [spdx-tech] Proposed modifications for Core Profile Template All, I did not see any conclusion on where we want to manage these files for tracking and discussing substantial edits so I am sending it to the list here. This is my proposed modifications to the Core Profile Template that Kay generously pulled together to start our conversations. I think this content makes sense for Core and the structure of this specific template could/should be used for the more general template applicable across profiles. I only focused on Classes in this pass and the full section of Properties still needs fleshed out though I would propose that its structure somewhat closely follow that of the Class section. Sean Barnum C – 703-473-8262 <mailto:[email protected]> [email protected] We are here to change the world! <https://www.facebook.com/MITREcorp> <https://www.linkedin.com/company/mitre> <https://twitter.com/MITREcorp> <https://www.youtube.com/user/mitrecorp> <https://plus.google.com/+MitreOrgFFRDCs/posts> <http://www.mitre.org/> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4017): https://lists.spdx.org/g/Spdx-tech/message/4017 Mute This Topic: https://lists.spdx.org/mt/81554060/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
