[Smwg] Service Package draft uploaded

[Anthony Crowson]

Erik, Wes,

With respect to alternatives to "terse" and "verbose", might I suggest "compact" and "complete" formats? Admittedly the words are rather similar, which makes abbreviation awkward, but I think they capture the sense and intent described in the document.

Anthony

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Barkley, Erik J (3970)
Sent: 05 June 2018 03:04
To: Eddy, Wesley M. (GRC-LCI0)[MTI SYSTEMS, INC.]; CCSDS SMWG ML (smwg at mailman.ccsds.org)
Subject: Re: [Smwg] Service Package draft uploaded

Wes,

My apologies for the delay in responding. For a first draft circulated to the working group, I think the document is in quite good shape. I do have a number of comments which are in the attached file. The more significant ones include:

a)      wrestling with terminology (I can't help but wonder if we want to come up with terms other than "terse" and "verbose" to better capture the functionality -- somewhat akin to the "core" aspect of the simple schedule format versus the extended aspect - I'll grant you that extended doesn't really help a whole lot either -- hence the wrestling with regard to terminology).

a.      This also ties in with a general concern of how to treat extenisiblity - I can't help but think that the SSF has set a good example and that this might be applicable here

b)     OID parameters directly in the class definition, especially as we are now talking about introducing names for the functional resource instances. This will also require further coordination with the working group in general but I just want to make sure this was noted.
CSSM Colleagues,

A request for everyone to please take a look and be prepared to discuss this at the June 12th teleconference.

Best regards,
-Erik

From: SMWG <smwg-bounces at mailman.ccsds.org> On Behalf Of Eddy, Wesley M. (GRC-LCI0)[MTI SYSTEMS, INC.]
Sent: Monday, March 26, 2018 8:17 AM
To: CCSDS SMWG ML (smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>
Subject: [Smwg] Service Package draft uploaded

Hello, I've uploaded a draft copy of the Service Package book to CWE.  It is based on the earlier draft JP had worked on, plus the XML schema document Marcin provided to me.

I have several comments embedded noting some differences between the document and the XML schema that I found.

Is it correct to assume that the XML schema that has been used in prototyping activity is more mature than the earlier draft and should take precedence (so we update the document to match the XSD file)?  If that is the case, there are only a small number of errors/issues that I found in the XSD file, that we can discuss.

One easy question I have is in the class OnlineServiceDetails, which has a field that I don't understand the purpose/usefulness of:
frequencyBand

Mandatory parameter.

Used to specify the frequency band that will be used by the service. If the frequency band is not relevant the value N/A (not applicable) shall be used.

*         C-Band

*         Ka-Band

*         Ku-Band

*         L-Band

*         S-Band

*         V-Band

*         X-Band

*         Optical

*         N/A

Enum

n/a


I believe that since the structure already contains an onlineConfigurationProfileXRef, that the frequencyBand value would be looked up via that anyways, and does not need to be included in the OnlineServiceDetails.  If someone else knows more than me and can either correct me, or confirm that this could be deleted, that would be helpful.

The draft document itself is at:
https://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS-SM%2FCWE%20Private%20-%20Beta%2FBook%20Production%2FBlue%2FService%20Package%20Data%20Formats%2FWhite%20Book%2FDrafts&FolderCTID=0x012000A2CFA608DF169C4EB988261660CEFAEB&View=%7BD853EDDB-F007-4BF6-8C31-BA03A9D0F4A4%7D&InitialTabId=Ribbon%2EDocument&VisibilityContext=WSSTabPersistence

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180605/4287f682/attachment.html>