mick said:
To answer your first question there, the two documents:
<image type="SPHERE"
tiled="true"
tiledimagewidth="8192"
tiledimageheight="4096"
tilesize="1024"
<sphere url="sphere_tiles_%v_%u.jpg" />
</image>
and
<image>
<type>SPHERE</type>
<tiled>true</tiled>
<tiledimagewidth>8192</tiledimagewidth>
<tiledimageheight>4096</tiledimageheight>
<tilesize>1024</tilesize>
<sphere>
<url>sphere_tiles_%v_%u.jpg</url>
</sphere>
</image>
are equivalent but not "the same". That is, they describe the
information with the same names, but using a different syntax.
See the XML FAQ at
http://xml.silmaril.ie/developers/attributes/ for
more on using attributes vs elements. My own rule is that numerical and
categorical data is best held in attributes, while normal text is best
held in elements, so I would prefer the first method for this data; but
there are probably many people who will disagree.
But you say that the Krpano docs say (on the first page of docs) "use
proper xml syntax". That's a different question. They must first tell
you what they mean by "proper".
XML can be used (and abused) for almost anything. The only sensible
meaning for "proper" here is "well-formed"; the rules for this are in
the XML Spec and are summarised in the XML FAQ at
http://xml.silmaril.ie/developers/validity/#wf
However, abuse of terminology is also rife, so Krpano may mean "XML
valid according to our Schema or DTD", which is one step further than
well-formedness. Valid documents are not only well-formed; they must
adhere to the specified structure and naming set out in a particular
Schema or DTD.
It is very rare that you are allowed just to make up your own XML and
expect some random application automagically to know what it means, so
you should check with the Krpano people as to what the "proper" XML is.
It appears from the thread you quote that there is already some
specified set of names (image, sphere, etc) that you are aware of, so
you presumably already know what you must use.
///Peter