-
Notifications
You must be signed in to change notification settings - Fork 0
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
Terms and Definitions Format #117
Comments
@ERyan71258 See https://doc.smpte-doc.org/st429-2-private/main/#sec-terms-and-definitions for an example. |
Partway there. Example of a term that is defined by its expanded version: Example of a term that is defined by its abbreviation: There should be actual definitions. The above two terms could instead be listed in an abbreviated terms list. The following are closer to what they should be, although they still need to be numbered: Unique Material Identifier Universally Unique Identifier eXtensible Markup Language Pertaining to the above four terms:
eXtensible Markup Language [SOURCE: W3C XML 1.0] We could make a case, however, for eliminating the definition and allowing your format, as it is less prone to error and neater. |
Some specific issues I see with the "Terms and definitions" clause, based on https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor208
|
Do you know why ISO requires terms to be numbered since the term itself is what is cited in the main body?
I am not a big fan of "notes to entry", esp. when they are used to convey requirements. Is it essential/useful for SMPTE to support? |
@ERyan71258 This is true when an acronym is defined. |
@ERyan71258 See note 1 to entry at https://doc.smpte-doc.org/st429-5-private/44ea72674f08696682194b6eb6d7307ce49867c5/ |
@ERyan71258 reading https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor208 it states: |
We need to clean up references to terms in other documents. I have found that the a referenced term is not always listed in the referenced document T&Ds. It is possible that it is defined within the body of the referenced document; however, that leaves the reader either wondering why no one confirmed that the term is defined in the referenced document, or having to search the document to see if the term is defined within the body of the document. There should be no uncertainty in a standard. As a best practice, all terms should be defined within the T&Ds. One project we should undertake is to map all of the T&D and normative reference dependencies, ensure that they are valid, and create a master list of T&Ds. |
That might be something we can automate actually, as Terms (if T&D clause or within the body text) are all wrapped (at least supposed to be) with |
As in link each use of the term within the document to its definition? That could work. I was thinking beyond the document itself, e.g., when a term in the T&Ds references the definition of a term in another document, that should be mapped. It would also include the terms in any normatively referenced document. Create a master list of all terms and definitions in all SMPTE standards documents, specifying the originating documents and dependencies on the original documents. If there are duplicate terms with differing definitions, then they are entered as separate terms, specifying the originating documents. Dependencies would be specified:
|
OOOOOOoOoooo. I really like this idea. I could really use this in my registry, scraping all |
And also create a map of normative reference dependencies, and even informative (Bibliography) dependencies. The normative reference chain can become complex. Having a clear record can simplify documentation. Case in point: I am in the 35PM DG IMF Application VC-5 drafting group (headed by Brian Schunck). Lars has considerably simplified the document by pointing out the document contained content that was already specified in the normative references. I would not be surprised to find circular references in both the T&D dependencies and the document dependencies. References to non-SMPTE documents should be included as well. IEEE provides a link to Google Scholar, from which we can search for citations of our documents. That would be a very cool thing to add. |
I have this all already. See https://stevellamb.github.io/mediastandards-registry/index.html#SMPTE.ST429-2.2020 and https://stevellamb.github.io/mediastandards-registry/dependancies/index.html#SMPTE.ST429-2.2020 for examples. I need to get the new documents in. Yes, now you are touching on my master plan for my registry and my not-at-all-hidden agenda I have explained to both Pierre and David. :) |
Hi Steve,
Excellent! We are so in need of this.
One small tweak: "Depend*a*ncies" is misspelled. Should be "Depend*e*ncies."
[image: image.png]
If not already included, perhaps add a circular reference detector and
citation generator.
The Terms and Definitions dependencies would follow a similar model and
also provide a master list of T&Ds.
Please feel free to tap me for input/feedback/testing.
All the best,
Ellen
…On Fri, May 24, 2024 at 12:56 PM Steve LLamb ***@***.***> wrote:
And also create a map of normative reference dependencies, and even
informative (Bibliography) dependencies.
I have this all already. See
https://stevellamb.github.io/mediastandards-registry/index.html#SMPTE.ST429-2.2020
and
https://stevellamb.github.io/mediastandards-registry/dependancies/index.html#SMPTE.ST429-2.2020
for examples. I need to get the new documents in.
Yes, now you are touching on my master plan for my registry and my
not-at-all-hidden agenda I have explained to both Pierre and David. :)
—
Reply to this email directly, view it on GitHub
<#117 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4KXDEHJFHS3JB3R6OFV7UDZD5WMXAVCNFSM6AAAAAAZJZYO2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZHE4TKMZTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Terms and Definitions shall be formatted as in the following samples:
3.1
picture
design or representation made by various means (such as painting, drawing, or photography)
Note 1 to entry: This definition can also include a digitally generated picture, and refers to the picture that one sees, as opposed to the digital representation as defined in 3.2.
Examples include displays in digital picture frames, images on computer or television monitors, and digital billboards.
[SOURCE: Merriam-Webster, modified — Note 1 to entry has been added.]
3.2
picture
all plane-stacks represented in a bitstream
[SOURCE: SMPTE ST 2117-1:2020]
3.3
symbol
member of a particular ordered collection of values having no duplicates within a single collection, i.e., member of any available alphabet
[SOURCE: SMPTE ST 2117-1:2020]
3.3.1
grandchild factor
4-bit code associated with a node in tableau-layer -2, -3 or -4, that specifies the occurrences of grandchild nodes of that node
[SOURCE: SMPTE ST 2117-1:2020]
3.3.2
resid-val
value of the label of a node, representing a residual-grid element explicitly
[SOURCE: SMPTE ST 2117-1:2020]
3.4
Society of Motion Picture and Television Engineers
SMPTE
organization that develops, documents and publishes media technology standards
Note that there should be a soft return after the term number, and if the term occupies more than one line (see 3.4), after the first line of the term, as well.
In addition, the terms cannot appear in the Table of Contents. You may need to create a workaround so that the numbered terms do not appear in the TOC.
The text was updated successfully, but these errors were encountered: