Greetings all,

 

I created the following pull requests for meeting minutes:

*       Friday  <https://github.com/spdx/meetings/pull/242> "Punch Down"
meeting minutes 4 November 2022
*       Minutes from Nov 1 2022 SPDX Tech Call
<https://github.com/spdx/meetings/pull/240> 
*       Decisions update from the 1 Nov 2022 tech call
<https://github.com/spdx/meetings/pull/241> 

 

We covered a lot of ground on our Friday's call.  We'll take the first part
of the tech team call this Tuesday to discuss and gain consent on decisions
made during the call.  Below is the list of decisions - for full details and
context, please see the minutes referenced above and the Puch List Issue #29
<https://github.com/spdx/spdx-3-model/issues/29> 

 

  * Core profile will have a union of all properties used in profiles for
the 3.0 release as opposed to a layered approach - profiles can add further
constraints on properties and we can have different namespaces for different
profiles.  Profiles can also create new classes not in core.  We will
revisit this decision prior to 3.0 release to make sure we didn't create too
much additional complexity.

  * ExternalIdentifier and ExternalReference will be concrete classes which
can also be subclassed

  * Core model will have the union of all enum values from profiles - we'll
check later if this creates a mess and revisit once all enum values are
collected

  * If trying to use a relationship type (or any enum), use other as the
relationship type, and use extension to provide detail of relationship type.
>From a spec perspective it's just other. From a tool implementer
perspective, if you want to be forward compatible, you can ignore
relationship types don't understand.

  * Adding to OTHER to hash algorithm enumeration & Comment to Integrity
method

  * Should Actor have its own identifier property? - William will clean the
model diagram for a discuss today

  * Relationships will be 1 to many type relationships

  * Keep the current 2.3 cardinality of relationship completeness - optional
with a default "Known"

  * Allow optional fields with defined default values

  * New items added:

    * Do we deprecate external reference types that are now covered by PURL?

    * Moving comment from element to CreationInfo

 

-------------------------------------------------

Gary O'Neall

Principal Consultant

Source Auditor Inc.

Mobile: 408.805.0586

Email:  <mailto:[email protected]> [email protected]

CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review,
re-transmission, dissemination or other use of, or taking of any action in
reliance upon this information by persons or entities other than the
intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.

 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4831): https://lists.spdx.org/g/Spdx-tech/message/4831
Mute This Topic: https://lists.spdx.org/mt/94855789/21656
Group Owner: [email protected]
Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to