Ian and me have already discussed this subject before. Basically I will use
the same
arguments to express our point of vue on this subject which is :
This is not allow by the MHEG-5 standard.
In the file startup, you have something like :
> {:ObjectRefVar
> 103
> :Shared true
> :OrigValue :ObjectRef ( '~/scene1.mhg' 23 )
> }
>
Chapter 51 ("referencing the MHEG-5 Objects"), it is not written that you
can refefrence an Ingredient of a scene ("~/scene1.mhg 23) within an
application object ("~/startup" 0).
Within an application object, the only kind of Ingredient allowed for
reference are the Ingredient of the Application group (case II.A)
Some will say : this is a reference and not a target, so it is allowed.
But see also chapter 50.1 ("ObjectReference") and you will see there is no
special case for the objectreference.
It is written :
This data type is used for referencing objects. The object referenced shall
be visible to the object from which the reference is made. This means that
the object shall be either an Application or Scene object, or shall be part
of either the active Application or the active Scene.
To be valid, ("~/scene1.mhg" 23) (the referenced object) shall be visible to
the object from which the reference is made ("~/startup" 103). This is
obviously not the case here. That means this is not valid.
> You should be able to see the logic of the code:
> - The application has an objectrefvariable that holds the reference to a
> text object in a scene. Note that the reference is to an object that is
> out of scope at this time.
> - When we transition to the scene we put the value of this variable into
> a variable in the scene (103). We then use this as an indirect target to
> change the content of the target. The value is now a target that is in
> scope.
>
I see the logic of the code but in our opinion, the spec does't match
suitably this kind of code. The first opinion is right as the spec is right
now :
> It could be argued that the variable in the application can not hold a
> reference to an object that is not in scope (hence it can only hold
> references to objects in the application or current scene) - to do
> otherwise is not valid.
>
>
Mickael BOULOUX
> --------------------------------------------------------------
> Mickaël Bouloux - tel: +33 (0)2 99 12 45 66 - CNET DSM/TAM/MMA
> FRANCE TELECOM - mailto:mickael.bouloux@cnet.francetelecom.fr
> --------------------------------------------------------------