From erik.j.barkley at jpl.nasa.gov Thu Apr 18 17:34:19 2019 From: erik.j.barkley at jpl.nasa.gov (Barkley, Erik J (3970)) Date: Thu, 18 Apr 2019 17:34:19 +0000 Subject: [Css-csts] CSS Area Spring 2019 meetings WG agendas Message-ID: CSSM and CSTS Colleagues, The consolidated CSS Area calendar for the Spring 2019 meetings is attached. The WG specific agendas have been posted and are available on the CCSDS spring meetings agendas web page via https://public.ccsds.org/meetings/2019Spring/2019SpringAgendas.aspx . I look forward to seeing those attending the meetings. Best regards, -Erik -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: d1-CSS-AreaCalendar-Spring- 2019.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 18589 bytes Desc: d1-CSS-AreaCalendar-Spring- 2019.xlsx URL: From john.pietras at gst.com Mon Apr 29 14:00:27 2019 From: john.pietras at gst.com (John Pietras) Date: Mon, 29 Apr 2019 14:00:27 +0000 Subject: [Css-csts] Typo in 3.11.2.2.4.3 of SFW Pink Book (pseudo RID) Message-ID: Dear Wolfgang, I believe that there's a typo in 3.11.2.2.4.3 of the CSTS SFW Pink Book. In the second to last sentence, I believe the reference for the SvcProdcutionStatusVersion1Type should be to F3.17, not F3.16. Best regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.pietras at gst.com Mon Apr 29 15:30:01 2019 From: john.pietras at gst.com (John Pietras) Date: Mon, 29 Apr 2019 15:30:01 +0000 Subject: [Css-csts] Allowed values for eventValue in Table A-23 (NOTIFY Invocation) of SFW Pink Book (pseudo RID) Message-ID: Allowed Value (AV) 53 (page A-28) of the CSTS SFW states "The value of the notifyInv-6 [eventValue] parameter can be one of the following: any value that can be expressed using the type SequenceOfQualifiedValue defined in F3.3, ...". That was true when the 'valid' values of SequenceOfQualifiedValue was defined in terms of a specific set of primitive data types (TypeAndValue). However, TypeAndValue has been recast as type Embedded (EMBEDDED PDV). As currently written AV53 allows any EMBEDDED PDV to be used for an eventValue. AV53 should be rephrased to restrict the values to the subset of EMBEDDED PDV types that correspond to eventValue types. That may require some wordsmithing to avoid a circular definition. Note that this also affects the FF-CSTS book. -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.pietras at gst.com Tue Apr 30 15:26:27 2019 From: john.pietras at gst.com (John Pietras) Date: Tue, 30 Apr 2019 15:26:27 +0000 Subject: [Css-csts] directive-qualifier for the 'reset' directive (pseudo RID) Message-ID: The Sequence-Controlled DP procedure extends the EXECUTE-DIRECTIVE operation (4.8.4.4) with the 'reset' directive (4.8.4.4.2) and associated directive-qualifier (4.8.4.4.3). The current phrasing of 4.8.4.4.3.1 states "The directive-qualifier shall identify the next-data-id parameter value ...". Although it should be obvious that this is *only* true when the directive-identifier is 'reset', it doesn't explicitly state that and could be interpreted as normatively requiring that the directive-qualifier have this value for *all* directive-identifiers. Elsewhere in the SFW, where extension elements are added in (name: value/qualifier) pairs, the value/qualifier specification is conditional on the value of the "name". I recommend that this be used here by changing the current wording to: "For the 'reset' (directive-identifier) directive, the directive-qualifier shall identify the next-data-id parameter value ...". I don't know if there are other instances of such unconditional specifications of extension values/qualifiers, but if there are they should be modified in the same manner. Best regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: