> I think it is good style not to use "~/startup" in the Application object's
> grp. identifier because it makes it more difficult to maintain MHEG objects
> when there are more than one application (applies only to such cases where
> this is an issue).
>
I think in a quite opposite way.
First, I assume the MHEG objects are in an ASN.1 DER format. Second, the
actual object location (ie. directory) is not fixed until final use:
Suppose a real broadcast situation. Broadcast programme schedule may change
at any moment.
Then, if a path is hard coded, you cannot change the programme unless you
decode an MHEG object, change the path and re-encode the object.
> I am quite sure, however, that the scope of the application is still clear
> because that part of the MHEG Engine which loads MHEG Group files and
> content data into the MHEG Engine (You might call it Object/Content
> Retrieval component) will still know the correct scope of the application.
> The scope becomes clear in the Launch or Spawn actuion which starts the
new
> application. The Grp. Identifer encoded in the Target of that action needs
> to include the complete path.
>
The last point is quite right. So, in a broadcast situation, maybe you
would prefer to use an indirect reference in conjunctiopn with the SI data
which indicates the latest programme info.
Regards,
Kei Takikawa
************************************************************
Kei Takikawa $B!JBl@n!!7<!K(J
NTT Software Corporation, JAPAN
Tel: +81 45 212 7986
Fax: +81 45 212 7524
e-mail: takikawa@po.ntts.co.jp
************************************************************