[Sis-ams] better subject-matching?

[Edell, David J.]

Tim,
 
Advanced filtering options could have potential usage, and if I remember
correctly are available to some degree in the software bus of Goddard's
cFE.  I don't think its worth the added processing costs to change to a
string-based subject ID to accomplish that though.  
 
At a minimum, there's always the possibility of psuedo-filtering by
specifying ranges of subject-IDs for specific categories, which is
sometimes done on its own to organize ID listings.  This becomes an
implementation choice within a program though, rather than a
specification.  
 
I think the SubjectID, UnitID, RoleID field combination is intended to
give a similar effect in combination with the "all subject" and "all
role" subscription types.  It's been a while since I've looked at these
field definitions though, so I could be wrong.   This might be another
topic for discussion at Berlin.
 
- David
 
 
 
________________________________

From: sis-ams-bounces at mailman.ccsds.org
[mailto:sis-ams-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J.
(GSFC-583.0)
Sent: Wednesday, September 10, 2008 6:15 PM
To: sis-ams at mailman.ccsds.org
Subject: [Sis-ams] better subject-matching?



Hello all,

 

Does anyone see a (worthwhile) benefit to enhancing our subject-matching
capabilities to allow hierarchical subject-ids and some
pattern-matching?  Subjects would be transmitted as character strings
rather than 2-byte numbers, and subscribers would be able to specify
some sort of regular-expression format.

 

For example, if there were these subjects:

        Attitude.sun_sensor

        Attitude.momentum_wheel

        Attitude.gyros

 

Then an application might subscribe to   attitude.*   to receive all
subjects within the 'attitude' domain.

 

I don't think this enhancement is needed for the typical NASA/Goddard
mission, nor are any missions (that I'm aware of) asking for it.  Still,
it seems like something worth considering.  Does anyone have an opinion?

 

Tim

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-ams/attachments/20080910/1fd9d242/attachment.html