[Smwg] Registries for Simple Schedule. (Our action from yesterdays webex)

[Shames, Peter M (312B)]

I was not trying to deal with these topics, since they are more down in
the weeds.  However, if you think these are items we should address now,
perhaps in one or more annexes, please propose an approach.

Peter


On 4/20/15, 5:12 PM, "Barkley, Erik J (3970)"
<erik.j.barkley at jpl.nasa.gov> wrote:

>Peter,
>
>I took a quick look at the draft registration policy and it is
>interesting and promising, but I don't think it is quite to the point yet
>of addressing the questions that Colin has here. In particular, I don't
>see anything about naming conventions for identifier registries  or
>packaging conventions for things like collection of schema files for the
>XML registries.  
>
>Best regards,
>
>-Erik
>
> -----Original Message-----
>From: Shames, Peter M (312B)
>Sent: Wednesday, April 15, 2015 7:58 AM
>To: Colin.Haddow at esa.int; John Pietras
>Cc: Barkley, Erik J (3970); CCSDS Service Mgmt WG
>Subject: Re: [Smwg] Registries for Simple Schedule. (Our action from
>yesterdays webex)
>
>Hi Colin,
>
>Strange that you should bring this up.  In the SEA I've been doing some
>analysis of the SANA registries just because there are actually already
>several "organization" and "person" type registries.  The attached paper
>is the proposal that I have drafted to deal with this.
>
>Please take a look and see if this approach, or something like it, will
>serve the purpose that you have identified.
>
>Thanks, Peter
>
>
>
>On 4/15/15, 6:21 AM, "Colin.Haddow at esa.int" <Colin.Haddow at esa.int> wrote:
>
>>
>>Hi John,
>>                 currently in the Simple Schedule book the following
>>repositories are identified;
>>
>>   SCCS-SM originatingOrganization
>>   SCCS-SM user (which cross-references the SANA Spacecraft Identifiers
>>   Registry)
>>   SCCS-SM stationAndAntennaRef
>>
>>Now I've had a look at the SANA procedures yellow book and can't see
>>anything related to naming conventions so it looks like we're
>>relatively free in that respect. I've also had a look at what the nav
>>and data archive guys are doing with thier XML schemas in the registry
>>and they're putting all the schemas under one registry (as you're
>>probably aware). This being the case I suggest the following approach;
>>
>>for the Schemas we create the following registry;
>>
>>SCCS-SM Data Entity XML Schemas - this would have the following
>>structure;
>>
>>File                    Description
>>Reference
>>The schema file [Type: FILE]  A textual description of the schema purpose
>>[Type:: STRING*1024]    Reference number of the appropriate book where
>>the
>>schema is defined [Type: STRING*16]
>>
>>
>>for the registries from the Simple Schedule book I'd rename these
>>slightly to remove the concatenation/camel case (will need a minor edit
>>to the book) such that these become;
>>
>>SCCS-SM Originating Organization
>>SCCS-SM User
>>SCCS-SM Station and Antenna Reference
>>
>>This approach should be extensible to handle any other registries that
>>we are likely to come up with in the scope of Service Management. Only
>>question I have (and perhaps Erik and Margherita can comment on this)
>>is whether it is better to use the Area, rather than the working group
>>as the initial identifier (i.e. replace SCCS-SM in the above registry
>>names with CSS).
>>The
>>latter approach would perhaps be more consistent with maintaining the
>>registries/schemas at Area level as has been discussed.
>>
>>Any thoughts ?
>>
>>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
>