[Css-csts] MD-CSTS W-0.07 on CWE

John Pietras john.pietras at gst.com
Tue Mar 3 16:34:27 EST 2009


CSTSWG colleagues -

 

I have uploaded the latest draft update of the Monitored Data CSTS
(MD-CSTS) Service Specification (MonitoredDataCSTS_W-0.07.doc) to the
CWE > Cross Support Services Area (CSS) <http://cwe.ccsds.org/css>  >
Documents <http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx>  >
CSS-CSTS
<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=http%3A%2F
%2Fcwe%2Eccsds%2Eorg%2Fcss%2Fdocs%2FCSS%2DCSTS>  > CWE Private
<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=http%3A%2F
%2Fcwe%2Eccsds%2Eorg%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private>  >
Future Services using Toolkit folder at

 

http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%2
0using%20Toolkit/MonitoredDataCSTS_W-0.07.doc

 (also at http://tinyurl.com/MD-CSTS-W0-07)

 

This version incorporates comments received at the Berlin meeting and
includes a strawman set of monitored parameter and notifiable event
types. The syntax of these parameter and event type names are
refinements of the approach that I outlined in the presentation that I
made in Berlin, and subsequently elaborated upon in my technical note
entitled "Functional Resources for the Monitored Data CSTS". In addition
to - and at least as important as - the parameter and event name types
themselves, this version specifies the way in which the functional
resource identifiers are to be defined. As described in the Berlin
briefing and the technical note, the functional resource identifiers
serve as name qualifiers, so that each reported monitored parameter
value and event notification has a distinguished name that unambiguously
identifies it.

 

Please note that the monitored parameter types and notifiable event
types themselves are strawman values. I fully expect any or all of them
to be changed, replaced, or deleted. The main purpose for including them
in the current MD-CSTS draft is to show how I propose to present these
definitions in the service specification. Assuming that the CSTSWG is
satisfied with the approach, the next step will be to evolve the set of
parameter and event types toward the "true" set of baseline types.

 

Best regards,

John

 

John Pietras

GST, Inc. 

7855 Walker Drive, Suite 200

Greenbelt, MD 20770

240-542-1155

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090303/ad1421fb/attachment.html


More information about the Css-csts mailing list