2020-08-04¶

Archived page

Read-only copy of the SPDX wiki. The wiki is no longer active; its content has moved to https://github.com/spdx. Last edited 2020-08-05 by K.stewart.

August 4, 2020

Attendees¶

Topics:

All students passed
Some issues making good progress on the generating Java code from XSD – more complex than we originally thought
Some issues with communications
Rishabh has been keeping a log on Google Docs which is a good practice
Kate will suggest on gitter that all students adopt this practice.

Funding goal for the SPDX online tools was achieved through community bridge
Enough funding for 14 months of hosting
A big Thank you to all supporters! https://funding.communitybridge.org/projects/f0e320d6-9c86-4656-ad4d-97842f25b124/financial
See meta issue for current status and progress https://github.com/spdx/spdx-online-tools/issues/199
Request to add SPDX document – see issue https://github.com/spdx/spdx-online-tools/issues/209
Thomas is also looking for funding through ACT for ORT
Discussed possibility of sharing infrastructure
Thomas suggested using Lightsail rather than RDS for the PostgreSQL database

Update to model
Added name to Artifact
Document proposal to break down into clauses
Constrained by ISO to not having sub-sections or clauses
Structure on subclasses
Suggested we having a naming standard for the clauses that indicate the subclasses
Structure
Moving external document references to the linking profile
Concern about requiring all the requirements of linking profile
- Possible 2 profiles, one for document linking and a stronger one for InToto
Concern about having required information for being able to link to a document
- General agreement
- Would like to simplify the approach language
- Several possible solutions including the PURL
SPDX Lite – should it be part of licensing or separate profile?
Suggestion to introduce pre-requisite profiles

Categories: Technical