[cssm] Updates:- Abstract Event Definition Book, Service Management Common data Entities Book, SMURF Book, UML Model, XML Schema.
Colin.Haddow at esa.int
Colin.Haddow at esa.int
Thu Jan 30 12:13:24 UTC 2020
Hi Hugh,
ok I've just had another look and your right.
Corrected version of the book uploaded to CWE and can be found at;
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.2%20-%20Service%20Management%20Common%20Data%20Entities.doc?Web=1
Changes are;
Correct typo in Ref. [3] version
Correct sections A.2.2, A.2.3 and A.2.4 to use Ref. [4] instead of [3].
Correct section A.2.2 to refer to section 3.11 (c) of Ref. [3]
Thanks for the sanity check
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
---------------------------------------------------------------------------------------------------------
From: "Hugh Kelliher" <hugh.kelliher at spaceconnexions.com>
To: <Colin.Haddow at esa.int>
Cc: <erik.j.barkley at jpl.nasa.gov>
Date: 30/01/2020 11:34
Subject: RE: [cssm] Updates:- Abstract Event Definition Book,
Service Management Common data Entities Book, SMURF Book, UML Model, XML
Schema.
Hi Colin,
Thanks for the quick reply. I can see now that I was getting mixed up
between ref[3] and ref[4].
My new question is, should the text be changed:
>From In accordance with reference [3], section 3.11 (c), updates to this
registry are at the discretion of CCSDS member agencies or registered
organizations, via the registered agency or organization representative.
To In accordance with reference [4], section 3.11 (c), .....
Just in passing, I see that reference [3], section 2.3 (c) is the same as
reference [4], section 3.11 (c).
In order to not restrict the register for orginatingOrganization to just a
service provider, could we reference section 3.3 rather than section
3.3.2.3 and leave it to the organization to chose which subsection is the
most relevant to them?
Cheers,
Hugh
From: Colin.Haddow at esa.int [mailto:Colin.Haddow at esa.int]
Sent: 30 January 2020 10:06
To: Hugh Kelliher
Cc: erik.j.barkley at jpl.nasa.gov
Subject: RE: [cssm] Updates:- Abstract Event Definition Book, Service
Management Common data Entities Book, SMURF Book, UML Model, XML Schema.
Hi Hugh,
reference [3] in the CDE is
[3] CCSDS SANA Registry Management Policy. Issue 2. CCSDS Record (Yellow
Book), CCSDS 313.1-Y-2. Washington, D.C.: CCSDS, May 2016.
This actually contains a typo as the published version is actual Issue 1,
so the reference should be
[3] CCSDS SANA Registry Management Policy. Issue 1. CCSDS Record (Yellow
Book), CCSDS 313.1-Y-1. Washington, D.C.: CCSDS, May 2016.
In this section 3.3.2.3 states;
3.3.2.3 Service Provider Registry
3.3.2.3.1 The subset of the CCSDS Organization Registry comprising Service
Providers
may be referred to as the Service Provider Registry.
3.3.2.3.2 The Review Authority for the Service Provider Registry shall be
the SSG.
3.3.2.3.3 The Registration Rule for the Service Provider Registry shall be
c) Change
requires no engineering review, but the request must come from the
Secretariat or an official
representative of a space agency that is a member of the CCSDS (cf.
reference [5]).
3.3.2.3.4 Only an AR with the Service Provider PoC role shall be permitted
to create,
update, or delete Service Provider Registry entries for that organization.
3.3.2.3.5 Each CCSDS Agency or CCSDS Affiliate Organization that provides
services
shall register in the CCSDS Organization Registry.
3.3.2.3.6 Each Service Provider organization will have a unique ISO OID
assigned by the
organization registration procedure.
3.3.2.3.7 Each Service Provider organization may have one or more service
sites.
3.3.2.3.8 Each service site shall be registered in the Service Site and
Aperture Registry.
3.3.2.3.9 Each Service Provider should provide a pointer (URN) for their
Service Catalog.
3.3.2.3.10 Each Service Provider should provide a reference to their
organizational PoC that
can provide information and commit to services.
3.3.2.3.11 The organizational PoC shall be registered in the Contacts
Registry.
I think this is the relevant part to reference although I guess you could
argue that if you are submitting a request, via the SMURF for example, for
a service then you are not necessarily also a service provider. That being
said I can't find a more suitable section in the Yellow book to
reference.The published version of the yellow book that I've got from the
CCSDS website doesn't have a section 3.11.
Erik, do you want me to correct the reference in the CDE book, or will you
do it (or is it the sort of thing that Tom catches) ?
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
---------------------------------------------------------------------------------------------------------
From: "Hugh Kelliher" <hugh.kelliher at spaceconnexions.com>
To: <Colin.Haddow at esa.int>
Date: 29/01/2020 20:26
Subject: RE: [cssm] Updates:- Abstract Event Definition Book,
Service Management Common data Entities Book, SMURF Book, UML Model, XML
Schema.
Hi Colin,
Did you also want to change the wording of CDE A.2.2
>From The policy that governs updates to the Organizational Roles registry
is that defined in subsection 3.3.2.3 of reference [3].
To In accordance with reference [3], section 3.11 (c), updates to this
registry are at the discretion of CCSDS member agencies or registered
organizations, via the registered agency or organization representative.
Cheers,
Hugh
Hugh Kelliher
Space ConneXions Ltd | www.spaceconnexions.com | +44 (0)1582 712418
Registered office: 10 Nettles Terrace, Guildford, Surrey, GU1 4PA, United
Kingdom
From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of
Colin.Haddow at esa.int
Sent: 23 January 2020 13:54
To: CCSDS Service Mgmt WG
Subject: [cssm] Updates:- Abstract Event Definition Book, Service
Management Common data Entities Book, SMURF Book, UML Model, XML Schema.
Dear all,
I've just uploaded the following updates to CWE;
Abstract Event Definition Book: Contains all RID
updates + changes to schema naming convention + SANA Registry paths.
Subject to AD review should be ready for publication.
Service Management Common Data Entities Book: Contains all RID
updates + changes to schema naming convention + SANA Registry paths.
Subject to AD review should be ready for publication.
SMURF Book Contains changes to
Basic start and duration constraints as discussed at last telecon (i.e.
merge into one constraint), change use of start and end time to optional
in ICS table + changes to schema naming convention + SANA Registry paths.
Does not (yet) contain any updates at the individual request type level
stating how the start and end times in the header should be used. I think
this update is perhaps best left until we're a bit further into the
prototyping.
XML Schemas: Contains the schemas
updated for the new naming convention and changes to the above books.
UML Model Contains the UML
model consistent with the changes to the above books.
These can be found at the following URLs
Abstract Event Definition Book:
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Red%20Book/Drafts/902x13r1_01.1%20-%20Abstract%20Event%20Definition.doc
Service Management Common Data Entities Book
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Red%20Book/Drafts/902x12r1_01.1%20-%20Service%20Management%20Common%20Data%20Entities.doc
SMURF Book
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Service%20Management%20Utilization%20Request%20Format/White%20Book/Drafts/902x9w0_10%20-%20Service%20Management%20Utilization%20Request%20Formats.doc
XML Schemas
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020200123.zip
UML Model
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020200123.zip
Note that I've not updated the CPIF with the new schema naming convention
and SANA Registry paths. As thats currently out for Agency review that
should be handled via a RID.
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 is intended only for the recipient(s) named above. It may
contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or
dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (dpo at esa.int).
This message is intended only for the recipient(s) named above. It may
contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or
dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (dpo at esa.int).
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20200130/be4cccb4/attachment-0001.htm>
More information about the SMWG
mailing list