questions about the XML Scheme and the 3th file example.
BramGo
here to ask some questions related to the ViPER fileformat. I have the
impression that there are a couple of obvious contradictions between
the XSD scheme and the 3 ViPER examples which are given at the
following website http://viper-toolkit.sourceforge.net/docs/file/ .
The website gives a XSD scheme which defines a couple of rules to the
format such as for example: according to the XSD scheme FILE-,
CONTENT- and OBJECT- tags should all have an ID attribute (not
optional), also a name (not optional) should be provided and a
framspan can (optional) be declared.
However in the third example there are several CONTENT-tags but none
of them has an ID attribute assigned. They do have a TIMESPAN
attribute assigned. But according to the XSD file a CONTENT-tag can
have a FRAMESPAN attribute, but not a TIMESPAN attribute. According to
the XSD file a TIMESPAN attribute is an attribute which is defined for
the data of a CONTENT tag but not the CONTENT tag itself.
Can I conclude that the ViPER format is still in development and not
really that fixed? Or should I conclude that the 3th example has some
errors? Or should I conclude that I made a mistake in my reasoning or
observartions somewhere?
Thank you in advance for all help.
Michael
On 1 Apr., 22:11, "BramGo" <bvanden...@gmail.com> wrote:
> Hi, I am new to this mailinglist. I hope I am at the correct address
> here to ask some questions related to the ViPER fileformat.
I think it is the only one ;-) It's a pity there's so little activity
though...
I have the
> impression that there are a couple of obvious contradictions between
> the XSD scheme and the 3 ViPER examples which are given at the
> following websitehttp://viper-toolkit.sourceforge.net/docs/file/.
I have the impression that there exist a couple of different
documentations representing different stages of the project. Perhaps
it's best to stick to the code?!
>
> The website gives a XSD scheme which defines a couple of rules to the
> format such as for example: according to the XSD scheme FILE-,
> CONTENT- and OBJECT- tags should all have an ID attribute (not
> optional), also a name (not optional) should be provided and a
> framspan can (optional) be declared.
>
> However in the third example there are several CONTENT-tags but none
> of them has an ID attribute assigned. They do have a TIMESPAN
> attribute assigned. But according to the XSD file a CONTENT-tag can
> have a FRAMESPAN attribute, but not a TIMESPAN attribute. According to
> the XSD file a TIMESPAN attribute is an attribute which is defined for
> the data of a CONTENT tag but not the CONTENT tag itself.
>
I'll attache a xml file that is produced by the current Viper GT which
is different again. There must still be some inconsistencies regarding
the file format, because Viper PE says "No FILE Information descriptor
has no SOURCEFILES attribute. No SOURCEFILES attribute found." on this
file. Anyhow, it continues to work...
> Can I conclude that the ViPER format is still in development and not
> really that fixed?
Uhmm, no and yes. It looks like ViPER was deserted while still in
development. At least no one answers to mails anymore. On the other
hand sourceforge shows increasing interest in ViPER, so perhaps this
group can kind of keep the project alive. It is a fantastic programm!
Hope that helps,
Michael
----
truth.xml sample:
<?xml version="1.0" encoding="UTF-8"?>
<viper xmlns="http://lamp.cfar.umd.edu/viper#" xmlns:data="http://
lamp.cfar.umd.edu/viperdata#">
<config>
<descriptor name="Information" type="FILE">
<attribute dynamic="false" name="SOURCETYPE" type="http://
lamp.cfar.umd.edu/viperdata#lvalue">
<data:lvalue-possibles>
<data:lvalue-enum value="SEQUENCE"/>
<data:lvalue-enum value="FRAMES"/>
</data:lvalue-possibles>
</attribute>
<attribute dynamic="false" name="NUMFRAMES" type="http://
lamp.cfar.umd.edu/viperdata#dvalue"/>
<attribute dynamic="false" name="FRAMERATE" type="http://
lamp.cfar.umd.edu/viperdata#fvalue"/>
<attribute dynamic="false" name="H-FRAME-SIZE"
type="http://lamp.cfar.umd.edu/viperdata#dvalue"/>
<attribute dynamic="false" name="V-FRAME-SIZE"
type="http://lamp.cfar.umd.edu/viperdata#dvalue"/>
</descriptor>
<descriptor name="Person" type="OBJECT">
<attribute dynamic="true" name="Location" type="http://
lamp.cfar.umd.edu/viperdata#bbox"/>
<attribute dynamic="false" name="Name" type="http://
lamp.cfar.umd.edu/viperdata#svalue"/>
</descriptor>
</config>
<data>
<sourcefile filename="file:/D:/Mreuss/viper-full-20060131/
samples/media/LAMP-Moving.mpeg">
<file id="0" name="Information">
<attribute name="SOURCETYPE">
<data:lvalue value="FRAMES"/>
</attribute>
<attribute name="NUMFRAMES">
<data:dvalue value="122"/>
</attribute>
<attribute name="FRAMERATE">
<data:fvalue value="1.0"/>
</attribute>
<attribute name="H-FRAME-SIZE">
<data:dvalue value="352"/>
</attribute>
<attribute name="V-FRAME-SIZE">
<data:dvalue value="240"/>
</attribute>
</file>
<object framespan="1:74" id="0" name="Person">
<attribute name="Location">
<data:bbox framespan="1:1" height="113" width="59"
x="215" y="76"/>
<data:bbox framespan="2:2" height="113" width="59"
x="212" y="76"/>
<data:bbox framespan="3:3" height="113" width="59"
x="210" y="76"/>
<data:bbox framespan="4:4" height="113" width="59"
[...]
<data:bbox framespan="73:73" height="123"
width="68"
x="38" y="78"/>
<data:bbox framespan="74:74" height="124"
width="69"
x="36" y="79"/>
</attribute>
<attribute name="Name">
<data:svalue value="eins"/>
</attribute>
</object>
<object framespan="1:92" id="1" name="Person">
<attribute name="Location">
<data:bbox framespan="1:46" height="143"
width="54"
x="116" y="68"/>
<data:bbox framespan="47:47" height="143"
width="55"
x="116" y="67"/>
<data:bbox framespan="48:48" height="144"
width="56"
x="116" y="67"/>
<data:bbox framespan="49:49" height="144"
width="57"
[...]
<data:bbox framespan="90:90" height="165"
width="103" x="126" y="65"/>
<data:bbox framespan="91:92" height="166"
width="105" x="127" y="65"/>
</attribute>
<attribute name="Name">
<data:svalue value="zwei"/>
</attribute>
</object>
</sourcefile>
</data>
</viper>