Skip to content

Added clarification to clause 10.3.1 General #16

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.

Sign up for GitHub

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

Closed
tbause wants to merge 4 commits into from
Closed

Added clarification to clause 10.3.1 General #16

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e291437
Added clarification to clause 10.3.1 General on
tbause May 9, 2023
15ca774
Fixed typos
tbause May 9, 2023
b245e7d
Merge branch 'main' into issues/0015-Clarify-Part-Number-Assignment
SteveLLamb May 9, 2023
b8dc221
updates as per convo with Thomas
SteveLLamb Jul 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion doc/main.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,7 +289,13 @@ <h3>Parts</h3>
<h4>General</h4>
<p>
Closely related Engineering Documents may be created as Parts. A Part of a document is a separate Engineering Document and shall be shown to be related to other
by using the same root document number plus a suffix of a hyphen and the Part number to distinguish among Parts (e.g. <code>1020-2:2009</code>, indicating document 1020, Part 2).
by using the same root document number plus a suffix of a hyphen and the Part number to distinguish among Parts (e.g. <code>1020-2:2009</code>, indicating document 1020, Part 2).
</p>
<p>
Part numbers should be continuously ascending from document to document (e.g. <code>1020-1:2009</code>, <code>1020-2:2011</code>, <code>1020-3:2012</code>) unless part numbers are used to organize large sets of multi-part documents.
</p>
<p>
The TC Chair shall assign document numbers in consultation with the document editor. Part numbers may be assigned at the request of the document editor at any time after a Project is approved and shall be assigned before a Final Committee Draft ballot is issued.
Comment thread
SteveLLamb marked this conversation as resolved.
Outdated
Copy link
Copy Markdown
Member

@palemieux palemieux May 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TC Chair is not a defined term, Technology Committee Chair(s) is the term.

I recommend that the Standards Director shall be responsible for assigning the part number in consultation with the Technology Committee Chair(s) since it is the Standards Director that maintains the database of documents.

Copy link
Copy Markdown
Member Author

@tbause tbause May 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not common practice and HO does not track part numbers until documents are published. HO is also not necessarily aware of the part number systems used in some efforts e.g. DC, IMF or SMPTE ST 2110 used to organize documents of a standards suite. HO can't make a judgement on where in such a part number system to place a document because it sometimes requires technical expertise. Additionally, we may not know the history about why certain part numbers are not used. The TC chair and the document editor or DG are better suite to do that. I prefer Steve's proposal.

Copy link
Copy Markdown
Member

@SteveLLamb SteveLLamb Jul 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@palemieux @tbause see b8dc221 for update as per discussion with Thomas today. Can wordsmith as needed.

</p>
</section>

Expand Down