-
Notifications
You must be signed in to change notification settings - Fork 143
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
Add ISO Foreword #1001
Add ISO Foreword #1001
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
docs/iso-foreword.md
Outdated
In the IEC, see | ||
[www.iec.ch/understanding-standards](https://www.iec.ch/understanding-standards). | ||
|
||
This document was prepared by the Object Management Group (OMG) (as SPDX® |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we be mentioning both organizations here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kestewart another one is The Linux Foundation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest using the following:
This document was prepared by The Linux Foundation under the SPDX Working Group (as SPDX® Specification v3.0.1) and drafted in accordance with its editorial rules. Its preparation and publication has been made in coordination with related efforts with the Object Management Group (OMG).
@bobmartin3000 @kestewart Are you comfortable with this phrasing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just added a comment with proposed edits to the language that @kestewart flagged. I'll ask also (but will defer to the tech team as I'm definitely not close to the details here!) -- it sounds like this language wouldn't be incorporated unless and until it's actually approved by ISO / JTC. Is that correct? Just making sure we aren't publishing something saying "this is approved by ISO" if it isn't actually yet. :) |
LGTM - Bob
From: Steve Winslow ***@***.***>
Date: Friday, August 9, 2024 at 3:55 PM
To: spdx/spdx-spec ***@***.***>
Cc: Robert A Martin ***@***.***>, Mention ***@***.***>
Subject: [EXT] Re: [spdx/spdx-spec] Add ISO Foreword (PR #1001)
@swinslow commented on this pull request. In docs/iso-foreword. md: > +Introduction and/or on the ISO list of patent declarations received +(see [www. iso. org/patents](https: //www. iso. org/patents)) or the IEC list of +patent declarations received
@swinslow commented on this pull request.
________________________________
In docs/iso-foreword.md<#1001 (comment)>:
+Introduction and/or on the ISO list of patent declarations received
+(see [www.iso.org/patents](https://www.iso.org/patents)) or the IEC list of
+patent declarations received (see [patents.iec.ch](https://patents.iec.ch)).
+
+Any trade name used in this document is information given for the convenience
+of users and does not constitute an endorsement.
+
+For an explanation of the voluntary nature of standards, the meaning of ISO
+specific terms and expressions related to conformity assessment, as well as
+information about ISO's adherence to the World Trade Organization (WTO)
+principles in the Technical Barriers to Trade (TBT), see
+[www.iso.org/iso/foreword.html](https://www.iso.org/iso/foreword.html).
+In the IEC, see
+[www.iec.ch/understanding-standards](https://www.iec.ch/understanding-standards).
+
+This document was prepared by the Object Management Group (OMG) (as SPDX®
I would suggest using the following:
This document was prepared by The Linux Foundation under the SPDX Working Group (as SPDX® Specification v3.0.1) and drafted in accordance with its editorial rules. Its preparation and publication has been made in coordination with related efforts with the Object Management Group (OMG).
@bobmartin3000</~https://github.com/bobmartin3000> @kestewart</~https://github.com/kestewart> Are you comfortable with this phrasing?
—
Reply to this email directly, view it on GitHub<#1001 (comment)>, or unsubscribe</~https://github.com/notifications/unsubscribe-auth/AUYBD7AKBDUPDKS6VIPZY53ZQUNBXAVCNFSM6AAAAABLNFC24KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMZQHE2TOMBSGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
That is the plan.
This would only appear in the document going to ISO.
Bob
From: Steve Winslow ***@***.***>
Date: Friday, August 9, 2024 at 3:57 PM
To: spdx/spdx-spec ***@***.***>
Cc: Robert A Martin ***@***.***>, Mention ***@***.***>
Subject: [EXT] Re: [spdx/spdx-spec] Add ISO Foreword (PR #1001)
I just added a comment with proposed edits to the language that @kestewart flagged. I'll ask also (but will defer to the tech team as I'm definitely not close to the details here!) -- it sounds like this language wouldn't be incorporated unless
I just added a comment with proposed edits to the language that @kestewart</~https://github.com/kestewart> flagged.
I'll ask also (but will defer to the tech team as I'm definitely not close to the details here!) -- it sounds like this language wouldn't be incorporated unless and until it's actually approved by ISO / JTC. Is that correct? Just making sure we aren't publishing something saying "this is approved by ISO" if it isn't actually yet. :)
—
Reply to this email directly, view it on GitHub<#1001 (comment)>, or unsubscribe</~https://github.com/notifications/unsubscribe-auth/AUYBD7FZZYKHKUKHFM6G473ZQUNJNAVCNFSM6AAAAABLNFC24KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGY2DSMZYGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Text from Bob's Word doc 2024-07-22 Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with this, thank you @bact!
This PR will supersede #974