[Smwg] Simple Schedule Recommendation - Draft Red 1.09.

Wed Jul 22 00:39:57 UTC 2015

Colin,

Below is an alternate wording suggestion.   Note that this starts to take on normative aspects which I think is appropriate for the new way of registry management that is emerging. We are in fact asking for certain behavior to be observed when dealing with registries.  Also, I'm not sure that we could assume an ICD will exist so I have a slightly different suggestion for the reserved prefix. But in general I think this is a good thing to include in the registries considerations section because I think we know quite well that there is nothing to prevent an implementation from using the recommendation "off label" and at least we have (or will have) relatively normative language in place to suggest how the "off label" usage goes and is kept separate from the "on label" approach.

Best regards,

-Erik

Suggested text:
Only values that have been registered should be used for the originatingOrganization,  user and apertureRef  parameters.   Unregistered values for the  originatingOrganization,  user and apertureRef  parameters, may be used. If unregistered values are used they should be prefixed with the string "UNR::".    Notes: i) "UNR::"  indicates an unregistered value; ii) this helps eliminate potential confusion in a multi-agency cross support context; iii) use of unregistered value is not recommended and should be avoided if possible. 

-----Original Message-----
From: smwg-bounces at mailman.ccsds.org [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Colin.Haddow at esa.int
Sent: Thursday, July 16, 2015 6:49 AM
To: John Pietras <john.pietras at gst.com>
Cc: CCSDS Service Mgmt WG <smwg at mailman.ccsds.org>; Holger.Dreihahn at esa.int
Subject: RE: [Smwg] Simple Schedule Recommendation - Draft Red 1.09.

Dear all,
                  at the last WebEx Anthony made a good suggestion about a naming convention for parameters that normally would be found in SANA but that for certain bilateral might be defined in an ICD. I've added an appropriate paragraph to the documents and uploaded it to SANA. This is version 1.11 (and is updated from Johns version 1.10).  Added para reads;

E2.5  Use Of Values Not Contained in The Registries

In certain circumstances users of this standard may wish to exchange schedule information  containing  values  for  the  originatingOrganization,  user and apertureRef  parameters  that  are  not  defined  in the registries discussed above.  To  avoid  conflict  with  values  obtained from the registries it is suggested  that these values be defined in an ICD agreed between the involved parties and that the values are prefixed with the string “ICD-“.

Cheers for now,

Colin

Doc URL is:
http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Schedule%20Format%20-%20xxx%20Book/902x1r1.11.doc

---------------------------------------------------------------------------------------------------------

Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,
Germany.

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int
---------------------------------------------------------------------------------------------------------

From:       John Pietras <john.pietras at gst.com>
To:         "Colin.Haddow at esa.int" <Colin.Haddow at esa.int>, CCSDS Service Mgmt
            WG <smwg at mailman.ccsds.org>,
Cc:         "Holger.Dreihahn at esa.int" <Holger.Dreihahn at esa.int>
Date:       15/07/2015 16:21
Subject:    RE: [Smwg] Simple Schedule Recommendation - Draft Red 1.09.

Colin and CSSMWG colleagues ---
I have made the last few updates to the XML-schema-related aspects of the Simple Schedule book and posted the result as version R-1.10 in the CWE > Cross Support Services Area (CSS) > Documents > CSS-SM > CWE Private > Schedule Format - xxx Book folder at URL http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Schedule%20Format%20-%20xxx%20Book/902x1r1.10.doc

These changes consist of:
a.  Changing the type of the' 'user' parameter from String[1024] to String [64] in table D-1; b. Replacing figure D-2, which now shows apertureRef instead of stationRef and antennaRef; c. Changing the value of apertureRef from "S-1" to "MGS_S-1" in Listing D-1, since the apertureRef must now unambiguously identify the aperture across all stations; d. Replacing D-3, the XML Spy Grid View of the example Simple Schedule in Listing D-1; and e. Adding trademark markings after instances of "XML Spy".

I have also made thenecessary changes to the XML schema files themselves and have uploaded them to the CWE > Cross Support Services Area (CSS) > Documents
> CSS-SM > Red Book XML Schemas folder:
http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DSM%2FRed%20Book%20XML%20Schemas&FolderCTID=0x012000A2CFA608DF169C4EB988261660CEFAEB&View=
{8045374D-F8E0-4356-83CA-993252A38FE8}

Best regards,
John

-----Original Message-----
From: smwg-bounces at mailman.ccsds.org [mailto:smwg-bounces at mailman.ccsds.org]
On Behalf Of Colin.Haddow at esa.int
Sent: Tuesday, July 14, 2015 5:06 AM
To: CCSDS Service Mgmt WG
Cc: Holger.Dreihahn at esa.int
Subject: [Smwg] Simple Schedule Recommendation - Draft Red 1.09.

Dear all,
                  I've just uploaded the latest draft of the Simple Schedule Red Book, this takes into account the changes that are ongoing with respect to the way which SANA registries are being managed at CCSDS level. This activity hasn't yet been completed so there are a couple of bits highlighted in yellow which will need to be sorted out later. Main impacts of these changes are that there are no longer any Simple Schedule dedicated repositories, all the information we require should be available in existing/in development registries, this has meant a few (relatively) minor tweaks to the data structure;

   stationRef and antennaRef have been replaced by one unique identifier,
   apertureRef
   Type,of originatingOrganization parameter is now string64
   Type of user parameter is now string64
   Type of apertureRef is string64

I've also tweaked the UML model a bit and various diagrams and text have been updated to reflect the changes required by the registry issue.

In the meantime, subject to the outstanding  points on the registries, I think we're pretty much finished except for John updating the XML schema.

What's the next step Erik ?, can we go to CESG yet ?

The document, model and diagrams can be found at the following URLs.

Document:
http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Schedule%20Format%20-%20xxx%20Book/902x1r1.09.doc
Model:
http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Schedule%20Format%20-%20xxx%20Book/902x1r1.09.mdzip
Diagrams:
http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Schedule%20Format%20-%20xxx%20Book/902x1r1.09.vsd

Cheers for now,

Colin

---------------------------------------------------------------------------------------------------------

Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,
Germany.

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int
---------------------------------------------------------------------------------------------------------

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

_______________________________________________
Smwg mailing list
Smwg at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/smwg

--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------

NOTE: This message was trained as non-spam.  If this is wrong, please correct the training as soon as possible.

Teach CanIt if this mail (ID 01OQ97bGC) is spam:
Spam:
https://filter.gst.com/canit/b.php?i=01OQ97bGC&m=47b49d538537&c=s
Not spam:
https://filter.gst.com/canit/b.php?i=01OQ97bGC&m=47b49d538537&c=n
Forget vote:
https://filter.gst.com/canit/b.php?i=01OQ97bGC&m=47b49d538537&c=f
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.