<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Re: use of .zip files<br>
<br>
As Don points out, there may be a directory (or more) plus lots of
files. It would then be necessary for the browser (perhaps null if
stand-alone app) + X3D application (either JavaScript or plug in)
to unzip and correctly store the component pieces. It would also
be necessary for the browser to identify all external from the
initial X3D file requests and properly change the reference to the
stored file. This would get really difficult if a Script node was
modifying a string pointing to an external file. <br>
<br>
This is something that was discussed over a decade ago. At that
time, the WG decided to not try to handle that because of that
difficulty. Browsers can handle compressed (i.e., gzipped) files.
This is done automatically with the server. Handling a ZIP file is
(a lot) more problematic. <br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote cite="mid:6408eae9-3590-1963-b49f-73b498faa729@nps.edu"
type="cite">Thanks Doug, good ideas, in some cases all taken care
of:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/wiki/index.php/X3D_MIME-Type#15._Other_Information.2FGeneral_Comment">http://www.web3d.org/wiki/index.php/X3D_MIME-Type#15._Other_Information.2FGeneral_Comment</a>
<br>
=========================================================================================
<br>
x3d-vrml files are encoded using utf-8.
<br>
<br>
The X3D standard is a continuation of the VRML standard that is
defined in RFC2077. As part of this work, several large
modifications were made to the file format and specification. The
basic premise for the specification continues the VRML design
rationale. The MIME types and file extensions were changed to
indicate this modified standard.
<br>
<br>
Content Sub-types
<br>
<br>
Each content type may have an additional Content-Encoding to
indicate whether the content has been compressed using GZIP in
addition to the basic textual encoding. This is also indicated by
modifying each file extension with the character "z". For example,
the plain text VRML-encoded file format would use the extension
".x3dv", and if compressed using GZIP uses the extension ".x3dvz".
<br>
=========================================================================================
<br>
<br>
and
<br>
<br>
X3D Scene Authoring Hints: Encodings
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Encodings">http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Encodings</a>
<br>
=========================================================================================
<br>
* X3D MIME Media Types are approved two-part identifiers for
X3D file formats on the Internet: x3d+xml, x3d-vrml and
x3d+fastinfoset.
<br>
* Name identifiers (DEF/USE and Prototype names), sometimes
referred to as fragment identifiers, must only use UTF-8
characters.
<br>
* Note that a variety of character encodings are possible for
the XML-based .x3d encoding (reference 19776-1 paragraph 4.4.1),
while only the utf8 character encoding is allowed for the
ClassicVRML .x3dv encoding.
<br>
* The Unicode FAQ UTF-8, UTF-16, UTF-32 & BOM contains
further information.
<br>
=========================================================================================
<br>
<br>
I suppose HelloWorld.x3d.zip might work unaltered when served, but
since the .zip extension implies that a directory archive might be
there (rather than a single file), we would need to do a little
more specification additions to handle it.
<br>
<br>
<br>
On 6/13/2016 5:29 AM, doug sanden wrote:
<br>
<blockquote type="cite">
<blockquote type="cite">MIME page
(<a class="moz-txt-link-freetext" href="http://www.web3d.org/wiki/index.php/X3D_MIME-Type">http://www.web3d.org/wiki/index.php/X3D_MIME-Type</a>) review
and update, particularly TODO: Deployment
<br>
</blockquote>
<br>
I don't know if you need to reserve it, but something like
model/web3d+zip might be interesting to some, as a way to bundle
resources and scene files in .zip like googleEarth kmz. Specs
haven't been discussed.
<br>
<br>
-Doug
<br>
<br>
<br>
more..
<br>
example possible web3dz format
<br>
-.web3z >>>
<br>
meta.xml <startscene type="vrml" path="/vrml/start.wrl"/>
<br>
/vrml start.wrl protos.wrl inline.wrl
<br>
/x3d
<br>
/json
<br>
/images
<br>
/video
<br>
/audio
<br>
/other
<br>
<<< .web3dz
<br>
<br>
more..
<br>
in freewrl I implemented a .x3z which I serve as MIMEtype
model/x3d+zip and is limited to doc.x3d start scene. It works
when the client has permission to write local files, and
permission to clean up those files after unzipping. The
implementation uses libminizip in the client, and desktop zip
utility to create the .zip file before renaming it to .x3z
<br>
<a class="moz-txt-link-freetext" href="http://dug9.users.sourceforge.net/web3d/tests/zipped/2_x3d.x3z">http://dug9.users.sourceforge.net/web3d/tests/zipped/2_x3d.x3z</a>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
x3d-public mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
<br>
<br>
</blockquote>
<br>
<br>
all the best, Don
<br>
</blockquote>
<br>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>