I'm sorry Guido, but I'm not sure to understand why my interpretation would
go the other way around compared to what Andreas answered about the
contentAvailable that would be never generated for Ingredients which have
no content.
In the meantime, trying to go deeper into the Preload/unload issue, I just
had two new questions coming in mind.
1. Regarding the provision of use that embarassed Andreas, I'm just asking
how the content attribute of an Ingredient could be Null. It seems to me
that any concrete class that inherits from the Ingredient Class either
defines the Content attribute as mandatory or not to be encoded at all. If
the content is mandatory, I don't see how it could be Null. Neither the
origContent attribute nor the setData elementary action accept Null, if I'm
right. In case the content shall not be encoded, it just concerns my second
question.
2. How the Null value shall be interpreted ? Should it be considered as a
specific value or as no value at all ? In other words, is it equivalent to
"void" ? In the specific case of Ingredient class content attribute, the
default value is "none". Should we considered that the default value (no
value) is equivalent to Null or shall an MHEG engine consider that no value
is different from Null ? I must admit that this is not completely clear in
my mind.
Anyway, I haven't participated to the meeting where MHEG-5 IS was discussed
and consequently have no clear idea about the intention that was behind
this provision of use for Preload/Unload actions. However, I guess it was
not intended to prevent Rectangle, DynamicLineArt or Hotspot to be prepared
or deleted by an action. At least, I hope... but I'm perhaps wrong...
Best regards,
__________________________________________________________________
Emmanuel BEUQUE mailto:ebeuque@pratique.fr
MediaServ tel: +33 (0) 2 99 64 35 64
Multimedia consultant & developer fax: +33 (0) 2 99 64 36 65