Hello Andreas and Kei!
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 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.
Example:
Application A:
some LinkEffect
Launch (("application-b/startup" 0))
Application B:
The file named ./application-b/startup :
{:Application
( "~/startup" 0)
}
--> Hence, while executing Application B", the MHEG Engine will internally
replace all "~" by "application-b".
BR Guido
-----------------------------------------------------------------
Guido Grassel guido.grassel@research.nokia.com
Nokia Research Center tel/fax: +358 9 4376-6827/6855
Multimedia Software Group mobile: +358 50 5876 126
mailing address: location:
P.O. Box 422 Itälahdenkatu 22b
FIN-00045 Nokia Group 00210 Helsinki-Lauttasaari
Finland
----------
From: EXT Andreas Kraft
To: mheg-ug
Subject: DAVIC GroupIdentifier
Date: 7. Augustta 1998 14:04
Dear MUG members,
during the conversion of test cases for the MHEG-7 WD we (i.e. Kei Takikawa
and
myself) had a small discussion concerning the use of the first shorthand
notation of the DAVIC GroupIdentifier. Maybe someone can help us here.
The question is whether it is allowed to use the shorthand notation
"~/startup" for the GroupIdentifier of an Application object. For example,
is the following object valid:
{:Application
( "~/startup" 0)
}
Kei thinks that this is valid because the scope of the application is valid
because it can be retrieved from the caller.
I think it is not because the Application object can not identify its scope
on its own.
What are your opinions?
Thanks in advance and best regards,
Andreas
--
o _ Andreas Kraft
(\_|_) GMD FOKUS, kraft@fokus.gmd.de, +49 30 3463-7232
T> ] [ The sky is the limit