<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR>
<STYLE>@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P.StyleParagraph4Kernat14pt {
FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.StyleParagraph4Kernat14pt {
FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.StyleParagraph4Kernat14pt {
FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
SPAN.EmailStyle18 {
COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2>Tim,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2>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.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2>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. </FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2>- David</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=637121722-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
sis-ams-bounces@mailman.ccsds.org [mailto:sis-ams-bounces@mailman.ccsds.org]
<B>On Behalf Of </B>Ray, Timothy J. (GSFC-583.0)<BR><B>Sent:</B> Wednesday,
September 10, 2008 6:15 PM<BR><B>To:</B>
sis-ams@mailman.ccsds.org<BR><B>Subject:</B> [Sis-ams] better
subject-matching?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hello all,</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">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.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">For example, if there were these
subjects:</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
Attitude.sun_sensor</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
Attitude.momentum_wheel</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
Attitude.gyros</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Then an application might subscribe
to attitude.* to receive all subjects within the
‘attitude’ domain.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">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?</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Tim</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P></DIV></BODY></HTML>