Started: 8/2/2007 10:26 PM by Barkley Erik
SMWG: List of Editorial Issues for Red-2
Base message thread for issues that are related to the editing of Red-2 and/or are not really significant from the point of view of major issues to be solved in development of Red-2
Posted: 8/2/2007 10:31 PM by Barkley Erik
Minor, subtle but important issue with respect to 'reuse" of parameters and applicable service agreement parameters:
 
In looking at the remodeled event sequencing information I came across the modulationIndex parameter definition all pointing to the same table.  However, there are in fact two distinct modulationIndex parameters with respect to the service agreement (forward carrier versus return carrier).  The table that defined the modulationIndex parameter for the return carrier did not call out the applicable service agreement parameters constraint.  The "source" table for the data set were modulationIndex is first defined referred to the forward carrier agreement information in the service agreement section.  We should double check this in other cases where the same parameter name is used in both the forward and return carrier sensing that the proper service agreement parameter is called out despite the fact that the general definition of the parameter is the same.