http://fileformats.archiveteam.org/api.php?action=feedcontributions&user=SwanQ&feedformat=atomJust Solve the File Format Problem - User contributions [en]2024-03-28T20:46:25ZUser contributionsMediaWiki 1.19.2http://fileformats.archiveteam.org/wiki/XLSBXLSB2019-11-19T20:49:55Z<p>SwanQ: changed link to MS-XLSB to go to new Microsoft Docs URL</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|subcat2=Spreadsheet<br />
|extensions={{ext|xlsb}}<br />
}}<br />
'''XLSB''' (Excel Binary) is one of the formats that [[Microsoft Excel|Excel]] spreadsheets can be saved under. It was introduced at the same time as the more common [[XLSX]] format which replaced the older [[XLS]]. XLS was a pure binary format, while XLSX is [[XML]]-based and its files are actually [[ZIP]] archives containing a number of sub-files related to the spreadsheet. XLSB is similar, in that it is actually a ZIP file (even though the extension is not .zip), but the main files within the ZIP are binary files with a .bin extension. There are also some other files within the ZIP including images and even some XML files, but the main content is in the binary files.<br />
<br />
== Format information ==<br />
* [https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-xlsb/acc8aa92-1f02-4167-99f5-84f9f676b95a?redirectedfrom=MSDN <nowiki>[MS-XLSB]</nowiki>: Excel (.xlsb) Binary File Format]<br />
* [http://www.arstdesign.com/articles/office2007bin.html Office 2007 .bin file format]<br />
* [http://www.arstdesign.com/BBS/BulletinBoard.php?qs_id=1355 Cracking the Office 2007 .bin file format]<br />
<br />
== Sample files ==<br />
* [http://www.spreadsheet1.com/2048-game-version-for-excel.html 2048 Game for Excel] is distributed in this format.<br />
<br />
== Other links ==<br />
* [http://blogs.msdn.com/b/dmahugh/archive/2006/08/22/712835.aspx New binary format for spreadsheets]<br />
* [http://blogs.msdn.com/b/davbosch/archive/2006/08/29/730183.aspx Excel 2007 Binary File Format (.xlsb) as a timesaver]<br />
<br />
[[Category:ZIP based file formats]]<br />
[[Category:Microsoft]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/Wavefront_OBJWavefront OBJ2019-09-18T13:24:23Z<p>SwanQ: /* Specifications */ fixed links to specs from O'Reilly</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=3D and CAD/CAM Models<br />
|extensions={{ext|obj}}, {{ext|mod}}<br />
|pronom={{PRONOM|fmt/1210}}<br />
}}<br />
[[Wavefront OBJ]] ('''OBJ''') is a 3D modeling format associated with Wavefront's Advanced Visualizer software.<br />
<br />
'''.obj''' files are plain text. There is also a binary formulation of the format, with extension '''.mod'''.<br />
<br />
OBJ files may reference external [[Wavefront MTL|"material"]] (.mtl) files.<br />
<br />
== Specifications ==<br />
* [http://resources.oreilly.com/examples/9781565920583/blob/master/CDROM/GFF/VENDSPEC/WAVEOBJ/OBJ_SPEC.PS OBJ_SPEC.PS]<br />
* [http://resources.oreilly.com/examples/9781565920583/blob/master/CDROM/GFF/VENDSPEC/WAVEOBJ/OBJ_SPEC.TXT OBJ_SPEC.TXT]<br />
* http://www.martinreddy.net/gfx/3d/OBJ.spec<br />
<br />
== Sample files ==<br />
* http://people.sc.fsu.edu/~jburkardt/data/obj/obj.html<br />
<br />
== Links ==<br />
* {{EGFF|wavefrontobj|Wavefront OBJ File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [[Wikipedia:Wavefront .obj file|Wikipedia: Wavefront .obj file]]<br />
* [[Wikipedia:The Advanced Visualizer|Wikipedia: The Advanced Visualizer]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/MEIMEI2019-05-05T19:03:29Z<p>SwanQ: /* External links */ updated link to sample files</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|extensions={{ext|mei}}<br />
}}<br />
The '''Music Encoding Initiative''' (MEI) is the name for an [[XML]] standard for music notation and the organization creating that standard. It is open source and its guidelines are released under the Educational Community License.<br />
<br />
== External links ==<br />
<br />
* [http://music-encoding.org/ Official website]<br />
* [https://music-encoding.org/guidelines/v3/content/ Guidelines for version 3.0.0]<br />
* [https://music-encoding.org/guidelines/v4/content/ Guidelines for version 4.0.0]<br />
* [https://github.com/music-encoding/sample-encodings Sample documents]<br />
<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/MEIMEI2019-05-05T18:55:28Z<p>SwanQ: fixed link to version 3 guidelines. Added link to version 4 guidelines</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|extensions={{ext|mei}}<br />
}}<br />
The '''Music Encoding Initiative''' (MEI) is the name for an [[XML]] standard for music notation and the organization creating that standard. It is open source and its guidelines are released under the Educational Community License.<br />
<br />
== External links ==<br />
<br />
* [http://music-encoding.org/ Official website]<br />
* [https://music-encoding.org/guidelines/v3/content/ Guidelines for version 3.0.0]<br />
* [https://music-encoding.org/guidelines/v4/content/ Guidelines for version 4.0.0]<br />
* [http://music-encoding.org/downloads/encodings/ Sample documents]<br />
<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/AccessAccess2017-04-16T13:47:40Z<p>SwanQ: /* Jet DB and Access Build Numbers */ replaced obsolete links to KB article 178880 with copy at IA</p>
<hr />
<div>{{FormatInfo<br />
| formattype=electronic<br />
| subcat=Databases<br />
| extensions={{ext|mdb}}<br />
| pronom={{PRONOM|x-fmt/66}}, {{PRONOM|x-fmt/238}}, {{PRONOM|x-fmt/239}}, {{PRONOM|x-fmt/240}}, {{PRONOM|x-fmt/241}}<br />
| released=1992<br />
}}<br />
<br />
'''Access''' released by '''Microsoft''' also known as '''Jet DB''' is a standalone database that forms part of the [[Microsoft Office]] Suite of productivity tools. It was first released in 1992. <br />
<br />
Access databases are composed of multiple page types. The length of these pages depends on the version of the Jet Database employed by the specific version of Microsoft Access. The first page of Access 95/97 and Access 2000/2003 databases is always a '''Database Definition Page'''.<br />
<br />
== Microsoft Access 95/97 - Jet 3 Database ==<br />
<br />
Microsoft Access 95/97 utilizes the Jet3 database engine. The page size of the Jet3 database engine is '''2048''' bytes. <br />
<br />
== Microsoft Access 2000/2002 - Jet 4 Database ==<br />
<br />
Microsoft Access 2000/2003 utilizes the Jet 4 database engine. The page size of the Jet4 database engine is '''4096''' bytes.<br />
<br />
== Internal structure of the format ==<br />
<br />
The Jet DB version can be found in the file header by reading the 4 byte little-endian integer at offset 0x13. Jet3 databases have a value of 0. Jet 4 databases have a value of 1.<br />
<br />
The version and build number of Microsoft Access used to create the file is stored in the format. These two values are stored within a [http://jabakobob.net/mdb/data-page.html LVAL Data Page] and deeper into that structure a [http://jabakobob.net/mdb/lvprop.html LvProp column] - part of the MSysObjects table. It is possible to extract this information from here alone, the complete MSysObject table definition is always the second page of the database (zero-based index). <br />
<br />
The block of data at offset 0x18 running for 126 bytes (Jet 3) and 128+ bytes (Jet 4) represents [[RC4]] encrypted data. It is thought this uses the key: '''0x6b39dac7'''.<br />
<br />
== Database Password ==<br />
<br />
'''Note:''' ''The information under this section should only be used by owners and custodians of databases where the password has been misplaced or lost and not for any illegal or illegitimate premises.'' <br />
<br/><br/><br />
Among other techniques Jet Databases employ a simple database password. The password field is '''0x42''' bytes into the file. Jet 3 database password fields are '''20 bytes''' in length, Jet 4 are '''40 bytes''' in length. <br />
<br/><br/><br />
'''Jet 3 Password'''<br />
<br />
XOR-ing the byte string running from 0x42 to 0x56 in a non-password protected database with that of a password protected database will reveal the password in plain text.<br />
<br />
Studying the Maxsoft tool under [http://fileformats.archiveteam.org/wiki/Access#Password_Tools Password Tools] will help users to understand how Access databases are protected.<br />
<br/><br/><br />
'''Jet 4 Password'''<br />
<br />
The Jet 4 password can be revealed similarly by XOR-ing the byte string running from 0x42 to 0x68. If after the XOR operation if you haven't an ASCII character, that is, you have a value greater than 0xFF you need to XOR that value again with a further key value (byte) at offset 0x54. <br />
<br />
Studying the Maxsoft tool under [http://fileformats.archiveteam.org/wiki/Access#Password_Tools Password Tools] will help users to understand how Access databases are protected.<br />
<br />
== Jet DB and Access Build Numbers ==<br />
<br />
The following table shows that the version of the Jet Database '''format''' remained fairly consistent between versions of Access:<br />
<br />
Client Application Jet Engine Used Recommended Jet DB Format<br />
------------------------- --------------- -------------------------<br />
Access 2.0 Jet 2.0 Jet 2.0<br />
Access 95 Jet 3.0 Jet 3.0<br />
Access 97 Jet 3.5 Jet 3.0<br />
Access 2000 Jet 4.0 Jet 4.0<br />
Access 2002 Jet 4.0 Jet 4.0<br />
<br />
The controller used to read and write the format by Access versions did change. The version of Access and its build number can help us to understand the version of the DLL used to interact with the format. The version and build number is embedded in the MDB objects (as described as part of its internal structure above) so can be easily extracted. Build numbers and DLL versions are described below ([http://support.microsoft.com/kb/248710 KB Article 248710] and [http://support.microsoft.com/kb/255275 KB Article 255275] and [http://support.microsoft.com/kb/291331 KB Article 291331]):<br />
<br />
Version File Version Patches<br />
-------------- ------------ -------<br />
Access 95 7.0 Unknown<br />
Access 97 8.0.3512 n/a <br />
Access 97 SR-1 8.0.4122 n/a<br />
Access 97 SR-2 8.0.5903 SR-1<br />
Access 2000 9.0.2720<br />
Access 2000 9.0.3821 SR-1<br />
Access 2000 9.0.4402 SR-1<br />
Access 2000 9.0.6926 SP-3<br />
Access 2002 10.0.2627.1<br />
Access 2002 10.0.3409.0 SP-1 <br />
Access 2002 10.0.4302.0 SP-2 <br />
Access 2002 10.0.6501.0 SP-3<br />
<br />
Access Version linked with MSJet35.dll ([http://support.microsoft.com/kb/248710 KB Article 248710]):<br />
<br />
Version DLL Version<br />
------- -----------<br />
Access 97 3.50.3428.0<br />
Access 97 SR-1 3.50.3907.5<br />
Access 97 SR-2 and Jet35Upd.exe (3rd rel) 3.51.2026.0<br />
<br />
The following table from [http://web.archive.org/web/20111115230803/http://support.microsoft.com/kb/178880 KB Article 178880] describes backward compatibility between Jet DB engines and MDB version:<br />
<br />
----------------------------------------------<br />
Jet Version 1.0 1.1 2.0 2.5 3.0 3.5<br />
----------------------------------------------<br />
MDB Version<br />
-----------<br />
1.0 Y Y Y Y Y Y<br />
1.1 N Y Y Y Y Y<br />
2.0 N N Y Y Y Y<br />
3.0 N N N N Y Y<br />
<br />
'''Note:''' See the [http://web.archive.org/web/20111115230803/http://support.microsoft.com/kb/178880 KB Article] for information on all DLL updates.<br />
<br />
== Specifications ==<br />
<br />
A formal specification from Microsoft has not been made available. The following links are attempts by third parties to reverse engineer and document the format:<br />
<br />
* [https://github.com/brianb/mdbtools/blob/master/HACKING Reverse engineered documentation used by mdbtools on GitHub]<br />
<br />
* [http://jabakobob.net/mdb/ Further documentation built on top of mdbtools' work]<br />
<br />
== Sample Files ==<br />
<br />
* [http://office.microsoft.com/en-ca/templates/results.aspx?qu=access&queryid=64492973-33dd-48c8-a228-6ffdf681fad6&avg=zac Microsoft.com: Sample Database Templates]<br />
<br />
* [http://www.utterangel.com/UtterAngel/utterangel.aspx?cat=acc utterangel.com: Sample Access Databases and Applications]<br />
<br />
* [https://isda.ncsa.uiuc.edu/NARA/CSR/php/search/formats.php?&cInput=mdb&srg=1&cName=default_extension&fid=866&fd=1&asc=1&num1=1 Conversion Software Registry: Sample Access Databases]<br />
<br />
== General Tools ==<br />
<br />
* [https://github.com/brianb/mdbtools Brian Bruns GutHub.com mdbtools]<br />
* [https://github.com/exponential-decay/MDBValidator MDBValidator: Tool to read and output the statistics of a Microsoft Access Database]<br />
<br />
== Password Tools ==<br />
<br />
* [http://planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73390&lngWId=1 Planet Source Code - Access Database Password Viewer]<br />
* [http://planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=72736&lngWId=1 Planet Source Code - Maxsoft Access Password Viewer]<br />
<br />
== References ==<br />
<br />
* [[Wikipedia:Microsoft_Access]]<br />
* [https://github.com/brianb/mdbtools/blob/master/HACKING Reverse engineered documentation used by mdbtools on GitHub]<br />
* [http://jabakobob.net/mdb/first-page.html Database definition and encryption key documentation]<br />
* [http://www.everythingaccess.com/tutorials.asp?ID=Jet-MDB-security---under-the-hood EverythingAccess.com Jet MDB Security - Under The Hood]<br />
<br />
== See Also == <br />
<br />
* [[Wikipedia:Microsoft_Jet_Database_Engine]]<br />
* [http://allenbrowne.com/ser-53.html Developer resource discussing DLL versions and sample code to retrieve Access version]<br />
* [http://www.techadre.com/content/microsoft-office-version-numbers-xp-2003-2007-2010 Site collating version and build numbers from XP through to 2010]<br />
* [http://en.wikibooks.org/wiki/JET_Database/Manipulation_tools Wikibooks Jet Database/Manipulation tools]<br />
* [http://webcheatsheet.com/SQL/access_specification.php WebCheatSheet.com Microsoft Access Specifications and Limitations]<br />
* [http://www.pcwelt.de/ratgeber/Geknackt-Microsoft-Money-99-504470.html PC Welt Germany discussing vulnerabilities in Microsoft Money 99 which is built on Jet DB 3.0]<br />
* [http://tutorialsto.com/view/printview-3771.html MDB Password View Tutorial]<br />
* [https://groups.google.com/forum/#!topic/pronom/_fz-eP0ge9o PRONOM Google Group Discussion about the distinction between Access versions in the PRONOM registry]<br />
* [http://www.textfiles.com/programming/FORMATS/q88173.txt ODBC Setup for Access and SQL Server]<br />
<br />
[[Category:Microsoft]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_DrawingOpenDocument Drawing2015-11-19T13:38:12Z<p>SwanQ: added links to ODF specs</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|odg}}, {{ext|fodg}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.graphics}}<br />
|locfdd={{LoCFDD|fdd000436}}<br />
|pronom={{PRONOM|fmt/139}}, {{PRONOM|fmt/296}}, {{PRONOM|fmt/297}}<br />
}}<br />
'''[[OpenDocument Drawing]]''' (also known as '''ODF Drawing''', '''OpenDocument Graphics''', or '''ODG''') is a vector graphics format intended for use with office applications. See [[OpenDocument]] for more information.<br />
<br />
== Disambiguation ==<br />
OpenDocument Drawing is distinct from the somewhat-mysterious format named [[OpenDocument Image]].<br />
<br />
== Identification ==<br />
OpenDocument Drawing files usually use [[ZIP]] as a container format. In that case, the ASCII string "<code>application/vnd.oasis.opendocument.graphics</code>" appears at offset 38.<br />
<br />
== Specifications ==<br />
* [http://www.oasis-open.org/committees/download.php/12572/OpenDocument-v1.0-os.pdf Official OpenDocument 1.0 spec]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 Official OpenDocument 1.1 spec]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 Official OpenDocument 1.2 spec]<br />
<br />
== Software ==<br />
* [[Wikipedia:OpenDocument software|Wikipedia: OpenDocument software]]<br />
* [http://libwpg.sourceforge.net/wpg2odg.htm libwpg / wpg2odg]<br />
<br />
[[Category:ZIP based file formats]]<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_DrawingOpenDocument Drawing2015-11-19T13:34:12Z<p>SwanQ: Added FDD link</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|odg}}, {{ext|fodg}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.graphics}}<br />
|locfdd={{LoCFDD|fdd000436}}<br />
|pronom={{PRONOM|fmt/139}}, {{PRONOM|fmt/296}}, {{PRONOM|fmt/297}}<br />
}}<br />
'''[[OpenDocument Drawing]]''' (also known as '''ODF Drawing''', '''OpenDocument Graphics''', or '''ODG''') is a vector graphics format intended for use with office applications. See [[OpenDocument]] for more information.<br />
<br />
== Disambiguation ==<br />
OpenDocument Drawing is distinct from the somewhat-mysterious format named [[OpenDocument Image]].<br />
<br />
== Identification ==<br />
OpenDocument Drawing files usually use [[ZIP]] as a container format. In that case, the ASCII string "<code>application/vnd.oasis.opendocument.graphics</code>" appears at offset 38.<br />
<br />
== Specifications ==<br />
* [http://www.oasis-open.org/committees/download.php/12572/OpenDocument-v1.0-os.pdf Official Open Document 1.0 spec]<br />
<br />
== Software ==<br />
* [[Wikipedia:OpenDocument software|Wikipedia: OpenDocument software]]<br />
* [http://libwpg.sourceforge.net/wpg2odg.htm libwpg / wpg2odg]<br />
<br />
[[Category:ZIP based file formats]]<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_TextOpenDocument Text2015-11-19T13:30:42Z<p>SwanQ: Added FDD links</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|extensions={{ext|fodt}}, {{ext|odt}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.text}}<br />
|locfdd={{LoCFDD|fdd000427}},{{LoCFDD|fdd000428}}<br />
|pronom={{PRONOM|fmt/136}},{{PRONOM|fmt/290}},{{PRONOM|fmt/291}}<br />
|released=2005-05-01<br />
}}<br />
The '''OpenDocument Text''' format is one of a number of types of the [[OpenDocument|Open Document Format for Office Applications]] (commonly referred to as OpenDocument), an [[XML]]-based file format defined by the Organization for the Advancement of Structured Information Standards (OASIS) in 2005.<br />
<br />
OpenDocument Text can, like all [[OpenDocument]] files, be represented in one of two fashions - as a single XML document or as a collection of several sub-documents within a single package (commonly a [[ZIP]] archive). Generally, the extension '''.fodt''' is used for the uncommonly-used single XML documents and '''.odt''' for packaged sub-documents.<br />
<br />
== Image embedding issue ==<br />
Both OpenOffice and LibreOffice are affected by a long-running bug where upon pasting an image into a document, only a ''hyperlink'' to the image is inserted by default (rather than the ''actual image data''). More details can be found [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice here]. This bug was first reported in 2004, and as of 2013 it still had not been resolved. It was apparently fixed in LibreOffice in early 2014 [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice].<br />
<br />
== Information ==<br />
<br />
* [https://www.oasis-open.org/standards#opendocumentv1.0 OpenDocument v1.0 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 OpenDocument v1.1 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 OpenDocument v1.2 specification]<br />
* [http://en.wikipedia.org/wiki/OpenDocument Wikipedia - OpenDocument]<br />
<br />
== Zipped Archive Structure ==<br />
<br />
When stored as a ZIP archive (with an .odt extension), it contains [[XML]] files describing text and relationships and [[JPEG]], [[PNG]], and other graphical files for pictures and other media included in the document.<br />
<br />
The layout of the regular ODT file is the following:<br />
* META-INF<br />
** manifest.xml<br />
* Thumbnails<br />
** thumbnail.png<br />
* content.xml<br />
* manifest.rdf<br />
* meta.xml<br />
* mimetype<br />
* settings.xml<br />
* styles.xml<br />
<br />
===Inner files description===<br />
====manifest.xml====<br />
Lists all the other xml files that are in this document. In the event of the simple document its contents maybe something like:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 1.0//EN" "Manifest.dtd"><br />
<manifest:manifest xmlns:manifest="urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"><br />
<manifest:file-entry manifest:media-type="application/vnd.oasis.opendocument.text" manifest:full-path="/"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="content.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="styles.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="meta.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="settings.xml"/><br />
</manifest:manifest><br />
<br />
====content.xml====<br />
This is the file that contains all the text in the document.<br />
<br />
The root element is always &lt;office:document-content&gt;. To get the text without metadata you go through the following hierarchy:<br />
* office:document-content<br />
** office:body<br />
*** office:text<br />
<br />
There you will find tags in the ''text'' namespace, that either mirror HTML in their names or are self-explanatory for the most part. Some examplese are:<br />
* text:p - paragraph<br />
* text:list - a listing that will have several text:list-item elements<br />
* text:list-item - a single item of the list<br />
<br />
Each text tag may have text:style attribute that links it to the style that is defined in office:document-content > office:automatic-styles > style:style.<br />
<br />
====manifest.rdf====<br />
[[RDF]] metadata. Most often the contents are just<br />
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
</rdf:RDF><br />
<br />
====meta.xml====<br />
This is the metadata that somebody fills in to describe the document or is automatically recorded by the software. The root element is always office:document-meta. The contents are defined rather loosely, the editing software is advised not to delete tags that it doesn't recognise, since other software maybe using them. In practice deleting all the contents of office:document-meta > office:meta will not damage the document, and it can be considered non-essential information.<br />
<br />
====mimetype====<br />
A text file that consists of<br />
application/vnd.oasis.opendocument.text<br />
<br />
====settings.xml====<br />
Software specific settings of the document. The root tag is &lt;office:document-settings&gt;. No inner contents are required for the functioning document.<br />
<br />
====styles.xml====<br />
Non-automatic document styles, that are held in &lt;office:document-styles&gt; tag.<br />
<br />
== Microsoft Office 2010 ==<br />
<br />
Microsoft Office 2010 seems to have some issues adhering to the OpenDocument standard. See the following link for more information;<br />
<br />
* [http://tbullock.comlore.com/2011/04/odf-12-support-in-microsoft-office.html Depth of Knowledge: ODF 1.2 Support in Microsoft Office] April 9, 2011<br />
<br />
== Microsoft Office 2013 ==<br />
<br />
Microsoft Office 2013 supports ODF 1.2. See the following links for more information;<br />
<br />
* [http://blogs.msdn.com/b/chrisrae/archive/2014/04/15/odf-1-2-enters-the-iso-standardization-process.aspx ODF 1.2 enters the ISO standardization process] April 15, 2014<br />
* [http://www.zdnet.com/article/microsofts-office-2013-odf-1-2-support-could-be-true-catalyst-for-openoffice-adoption/ Microsoft's Office 2013 ODF 1.2 support could be true catalyst for OpenOffice adoption] August 15, 2012<br />
<br />
== Sample files ==<br />
* [http://www.dan.info/sampledata/msword/testing.odt Sample document saved from Windows Word 2007]<br />
<br />
== Links ==<br />
* [http://blog.riemann.cc/2013/04/23/versioning-of-openoffice-libreoffice-documents-using-git/ Versioning of OpenOffice/LibreOffice Documents Using Git]<br />
* [http://wiki.opf-labs.org/display/TR/OpenDocument+Text OpenDocument Text entries in OPF File Format Risk Registry ]<br />
* [https://updegrove.wordpress.com/2014/03/12/odf-vs-ooxml-war-of-the-words/ ODF vs. OOXML: War of the Words]<br />
* [http://askubuntu.com/questions/60778/how-can-i-convert-an-odt-file-to-a-pdf How to convert ODT to PDF]<br />
<br />
[[Category:XML based file formats]]<br />
[[Category:ZIP based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocumentOpenDocument2015-11-19T13:27:56Z<p>SwanQ: Added FDD link</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|pronom={{PRONOM|fmt/135}}, others<br />
|locfdd={{LoCFDD|fdd000247}}, others<br />
|extensions={{ext|odm}}, {{ext|odt}}, {{ext|ods}}, {{ext|odg}}, {{ext|odp}}, {{ext|odc}}, {{ext|odi}}, {{ext|odf}}, {{ext|odb}}, {{ext|ott}}, {{ext|ots}}, {{ext|otg}}, {{ext|otp}}, {{ext|otc}}, {{ext|oti}}, {{ext|otf}}, {{ext|oth}}, {{ext|fodt}}, {{ext|fods}}, {{ext|fodg}}, {{ext|fodp}}<br />
|released=2005<br />
}}<br />
'''OpenDocument''', also known as '''Open Document Format for Office Applications''' or '''ODF''', is a family of file formats designed to be used by word processors, spreadsheet applications, and other office applications. These formats were developed by a group called OASIS, so they are sometimes referred to as "OASIS format" or "OASIS Open Document Format".<br />
<br />
== Formats ==<br />
=== Documents ===<br />
{| class="wikitable"<br />
! Format<br />
! MIME type<br />
! Extension<br />
! PRONOM<br />
|-<br />
|[[OpenDocument Text]]<br />
|{{mimetype|application/vnd.oasis.opendocument.tex}}<br />
|.odt, .fodt<br />
|{{PRONOM|fmt/136}}, {{PRONOM|fmt/290}}, {{PRONOM|fmt/291}}<br />
|-<br />
|[[OpenDocument Spreadsheet]]<br />
|{{mimetype|application/vnd.oasis.opendocument.spreadsheet}}<br />
|.ods, .fods<br />
|{{PRONOM|fmt/137}}, {{PRONOM|fmt/294}}, {{PRONOM|fmt/295}}<br />
|-<br />
|[[OpenDocument Drawing]]<br />
|{{mimetype|application/vnd.oasis.opendocument.graphics}}<br />
|.odg, .fodg<br />
|{{PRONOM|fmt/139}}, {{PRONOM|fmt/296}}, {{PRONOM|fmt/297}}<br />
|-<br />
|[[OpenDocument Presentation]]<br />
|{{mimetype|application/vnd.oasis.opendocument.presentation}}<br />
|.odp, .fodp<br />
|{{PRONOM|fmt/138}}, {{PRONOM|fmt/292}}, {{PRONOM|fmt/293}}<br />
|-<br />
|[[OpenDocument Chart]]<br />
|{{mimetype|application/vnd.oasis.opendocument.chart}}<br />
|.odc<br />
|<br />
|-<br />
|[[OpenDocument Image]]<br />
|{{mimetype|application/vnd.oasis.opendocument.image}}<br />
|.odi<br />
|<br />
|-<br />
|[[OpenDocument Formula]]<br />
|{{mimetype|application/vnd.oasis.opendocument.formula}}<br />
|.odf<br />
|<br />
|-<br />
|[[OpenDocument Database|OpenDocument Database Front End]]<br />
|{{mimetype|application/vnd.oasis.opendocument.base}}<br>{{mimetype|application/vnd.oasis.opendocument.database}}<br />
|.odb<br />
|{{PRONOM|fmt/140}}, {{PRONOM|fmt/444}}, {{PRONOM|fmt/424}}<br />
|}<br />
<br />
=== Templates ===<br />
{| class="wikitable"<br />
! Format<br />
! MIME type<br />
! Extension<br />
|-<br />
|[[OpenDocument Text Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.text-template}}<br />
|.ott<br />
|-<br />
|[[OpenDocument Spreadsheet Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.spreadsheet-template}}<br />
|.ots<br />
|-<br />
|[[OpenDocument Drawing Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.graphic-template}}<br />
|.otg<br />
|-<br />
|[[OpenDocument Presentation Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.presentation-template}}<br />
|.otp<br />
|-<br />
|[[OpenDocument Chart Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.chart-template}}<br />
|.otc<br />
|-<br />
|[[OpenDocument Image Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.image-template}}<br />
|.oti<br />
|-<br />
|[[OpenDocument Formula Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.formula-template}}<br />
|.otf<br />
|-<br />
|[[OpenDocument HTML Template]]<br />
|{{mimetype|application/vnd.oasis.opendocument.text-web}}<br />
|.oth<br />
|}<br />
<br />
=== Other ===<br />
{| class="wikitable"<br />
! Format<br />
! MIME type<br />
! Extension<br />
|-<br />
|Global Text Document<br />
|{{mimetype|application/vnd.oasis.opendocument.text-master}}<br />
|.odm<br />
|}<br />
<br />
== Identification ==<br />
In most cases, OpenDocument files begin with the ASCII string "<code>PK</code>", have "<code>mimetype</code>" at offset 30, and "<code>application/vnd.oasis.opendocument.</code>" at offset 38.<br />
<br />
== Specifications ==<br />
* [https://www.oasis-open.org/standards#opendocumentv1.0 OpenDocument v1.0 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 OpenDocument v1.1 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 OpenDocument v1.2 specification]<br />
<br />
== Software ==<br />
* [[Wikipedia:OpenDocument software|Wikipedia: OpenDocument software]]<br />
* [[Wikipedia:Comparison of OpenDocument software|Wikipedia: Comparison of OpenDocument software]]<br />
* [http://webodf.org/ WebODF]<br />
* [http://sourceforge.net/p/libwpd/wiki/libodfgen/ libodfgen library]<br />
* [https://incubator.apache.org/odftoolkit/ ODF Toolkit] (Java) including:<br />
** [https://incubator.apache.org/odftoolkit/conformance/ODFValidator.html ODF Validator] (a cloud-hosted version of the validator is running [https://odf-validator.rhcloud.com/ here].<br />
<br />
=== ODF version support over time ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | ODF version<br />
! scope="col" | Date of standard approval by OASIS<!-- intl. community wants intl iso standard date formats --><br />
! scope="col" | First supporting version of the software<br />
|-<br />
| | ODF 1.0<br />
| | 2005-05-01<br />
| | OpenOffice.org 1.1.5 or StarOffice 7<br />
|-<br />
| | ODF 1.1<br />
| | 2007-02-02<br />
| | OpenOffice.org 2.2 or StarOffice 8 Update 4<br />
|-<br />
| | ODF 1.2<br />
| | 2011-09-30<br />
| | OpenOffice.org 3, StarOffice 9, Oracle Open Office<br />
|-<br />
| | ODF 1.2 (Extended)<br />
| | -<br />
| | OpenOffice.org 3.2 or StarOffice 9.2<br />
|}<br />
<br />
Taken from [https://help.libreoffice.org/Common/XML_File_Formats|LibreOffice - XML File Formats].<br />
<br />
== Sample files ==<br />
* [http://craphound.com/homeland/Cory_Doctorow_-_Homeland.odt Homeland by Cory Doctorow]<br />
<br />
== Links ==<br />
* [[Wikipedia:OpenDocument|Wikipedia: OpenDocument]]<br />
* [[Wikipedia:OpenDocument technical specification|Wikipedia: OpenDocument technical specification]]<br />
* [http://www.opendocumentformat.org/ OpenDoc Society: opendocumentformat.org]<br />
* [http://www.forensicswiki.org/wiki/Open_Document_Format Forensic Wiki article]<br />
* [http://www.linux-magazine.com/Online/Features/LibreOffice-vs.-OpenOffice LibreOffice vs OpenOffice: Comparative review]<br />
* [http://m.theregister.co.uk/2014/01/30/uk_picks_open_document_format_for_all_government_files/ UK picks Open Document Format for all government files]<br />
* [http://classic.slashdot.org/story/14/07/02/1349208 WebODF: JavaScript Open Document Format Editor Deemed Stable] (Slashdot discussion)<br />
* [http://ask.libreoffice.org/en/question/648/is-it-possible-to-embed-fonts-in-a-writerimpresscalc-document/ Discussion of embedding fonts in ODF documents]<br />
<br />
[[Category:ZIP based file formats]]<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_TextOpenDocument Text2015-07-19T21:43:03Z<p>SwanQ: /* Microsoft Office 2010 */ added section on support in Office 2013</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|extensions={{ext|fodt}}, {{ext|odt}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.text}}<br />
|pronom={{PRONOM|fmt/136}},{{PRONOM|fmt/290}},{{PRONOM|fmt/291}}<br />
|released=2005-05-01<br />
}}<br />
The '''OpenDocument Text''' format is one of a number of types of the [[OpenDocument|Open Document Format for Office Applications]] (commonly referred to as OpenDocument), an [[XML]]-based file format defined by the Organization for the Advancement of Structured Information Standards (OASIS) in 2005.<br />
<br />
OpenDocument Text can, like all [[OpenDocument]] files, be represented in one of two fashions - as a single XML document or as a collection of several sub-documents within a single package (commonly a [[ZIP]] archive). Generally, the extension '''.fodt''' is used for the uncommonly-used single XML documents and '''.odt''' for packaged sub-documents.<br />
<br />
== Image embedding issue ==<br />
Both OpenOffice and LibreOffice are affected by a long-running bug where upon pasting an image into a document, only a ''hyperlink'' to the image is inserted by default (rather than the ''actual image data''). More details can be found [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice here]. This bug was first reported in 2004, and as of 2013 it still had not been resolved. It was apparently fixed in LibreOffice in early 2014 [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice].<br />
<br />
== Information ==<br />
<br />
* [https://www.oasis-open.org/standards#opendocumentv1.0 OpenDocument v1.0 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 OpenDocument v1.1 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 OpenDocument v1.2 specification]<br />
* [http://en.wikipedia.org/wiki/OpenDocument Wikipedia - OpenDocument]<br />
<br />
== Zipped Archive Structure ==<br />
<br />
When stored as a ZIP archive (with an .odt extension), it contains [[XML]] files describing text and relationships and [[JPEG]], [[PNG]], and other graphical files for pictures and other media included in the document.<br />
<br />
The layout of the regular ODT file is the following:<br />
* META-INF<br />
** manifest.xml<br />
* Thumbnails<br />
** thumbnail.png<br />
* content.xml<br />
* manifest.rdf<br />
* meta.xml<br />
* mimetype<br />
* settings.xml<br />
* styles.xml<br />
<br />
===Inner files description===<br />
====manifest.xml====<br />
Lists all the other xml files that are in this document. In the event of the simple document its contents maybe something like:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 1.0//EN" "Manifest.dtd"><br />
<manifest:manifest xmlns:manifest="urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"><br />
<manifest:file-entry manifest:media-type="application/vnd.oasis.opendocument.text" manifest:full-path="/"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="content.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="styles.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="meta.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="settings.xml"/><br />
</manifest:manifest><br />
<br />
====content.xml====<br />
This is the file that contains all the text in the document.<br />
<br />
The root element is always &lt;office:document-content&gt;. To get the text without metadata you go through the following hierarchy:<br />
* office:document-content<br />
** office:body<br />
*** office:text<br />
<br />
There you will find tags in the ''text'' namespace, that either mirror HTML in their names or are self-explanatory for the most part. Some examplese are:<br />
* text:p - paragraph<br />
* text:list - a listing that will have several text:list-item elements<br />
* text:list-item - a single item of the list<br />
<br />
Each text tag may have text:style attribute that links it to the style that is defined in office:document-content > office:automatic-styles > style:style.<br />
<br />
====manifest.rdf====<br />
[[RDF]] metadata. Most often the contents are just<br />
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
</rdf:RDF><br />
<br />
====meta.xml====<br />
This is the metadata that somebody fills in to describe the document or is automatically recorded by the software. The root element is always office:document-meta. The contents are defined rather loosely, the editing software is advised not to delete tags that it doesn't recognise, since other software maybe using them. In practice deleting all the contents of office:document-meta > office:meta will not damage the document, and it can be considered non-essential information.<br />
<br />
====mimetype====<br />
A text file that consists of<br />
application/vnd.oasis.opendocument.text<br />
<br />
====settings.xml====<br />
Software specific settings of the document. The root tag is &lt;office:document-settings&gt;. No inner contents are required for the functioning document.<br />
<br />
====styles.xml====<br />
Non-automatic document styles, that are held in &lt;office:document-styles&gt; tag.<br />
<br />
== Microsoft Office 2010 ==<br />
<br />
Microsoft Office 2010 seems to have some issues adhering to the OpenDocument standard. See the following link for more information;<br />
<br />
* [http://tbullock.comlore.com/2011/04/odf-12-support-in-microsoft-office.html Depth of Knowledge: ODF 1.2 Support in Microsoft Office] April 9, 2011<br />
<br />
== Microsoft Office 2013 ==<br />
<br />
Microsoft Office 2013 supports ODF 1.2. See the following links for more information;<br />
<br />
* [http://blogs.msdn.com/b/chrisrae/archive/2014/04/15/odf-1-2-enters-the-iso-standardization-process.aspx ODF 1.2 enters the ISO standardization process] April 15, 2014<br />
* [http://www.zdnet.com/article/microsofts-office-2013-odf-1-2-support-could-be-true-catalyst-for-openoffice-adoption/ Microsoft's Office 2013 ODF 1.2 support could be true catalyst for OpenOffice adoption] August 15, 2012<br />
<br />
== Sample files ==<br />
* [http://www.dan.info/sampledata/msword/testing.odt Sample document saved from Windows Word 2007]<br />
<br />
== Links ==<br />
* [http://blog.riemann.cc/2013/04/23/versioning-of-openoffice-libreoffice-documents-using-git/ Versioning of OpenOffice/LibreOffice Documents Using Git]<br />
* [http://wiki.opf-labs.org/display/TR/OpenDocument+Text OpenDocument Text entries in OPF File Format Risk Registry ]<br />
* [https://updegrove.wordpress.com/2014/03/12/odf-vs-ooxml-war-of-the-words/ ODF vs. OOXML: War of the Words]<br />
* [http://askubuntu.com/questions/60778/how-can-i-convert-an-odt-file-to-a-pdf How to convert ODT to PDF]<br />
<br />
[[Category:XML based file formats]]<br />
[[Category:ZIP based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_TextOpenDocument Text2015-07-19T21:13:52Z<p>SwanQ: /* Image embedding issue */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|extensions={{ext|fodt}}, {{ext|odt}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.text}}<br />
|pronom={{PRONOM|fmt/136}},{{PRONOM|fmt/290}},{{PRONOM|fmt/291}}<br />
|released=2005-05-01<br />
}}<br />
The '''OpenDocument Text''' format is one of a number of types of the [[OpenDocument|Open Document Format for Office Applications]] (commonly referred to as OpenDocument), an [[XML]]-based file format defined by the Organization for the Advancement of Structured Information Standards (OASIS) in 2005.<br />
<br />
OpenDocument Text can, like all [[OpenDocument]] files, be represented in one of two fashions - as a single XML document or as a collection of several sub-documents within a single package (commonly a [[ZIP]] archive). Generally, the extension '''.fodt''' is used for the uncommonly-used single XML documents and '''.odt''' for packaged sub-documents.<br />
<br />
== Image embedding issue ==<br />
Both OpenOffice and LibreOffice are affected by a long-running bug where upon pasting an image into a document, only a ''hyperlink'' to the image is inserted by default (rather than the ''actual image data''). More details can be found [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice here]. This bug was first reported in 2004, and as of 2013 it still had not been resolved. It was apparently fixed in LibreOffice in early 2014 [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice].<br />
<br />
== Information ==<br />
<br />
* [https://www.oasis-open.org/standards#opendocumentv1.0 OpenDocument v1.0 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 OpenDocument v1.1 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 OpenDocument v1.2 specification]<br />
* [http://en.wikipedia.org/wiki/OpenDocument Wikipedia - OpenDocument]<br />
<br />
== Zipped Archive Structure ==<br />
<br />
When stored as a ZIP archive (with an .odt extension), it contains [[XML]] files describing text and relationships and [[JPEG]], [[PNG]], and other graphical files for pictures and other media included in the document.<br />
<br />
The layout of the regular ODT file is the following:<br />
* META-INF<br />
** manifest.xml<br />
* Thumbnails<br />
** thumbnail.png<br />
* content.xml<br />
* manifest.rdf<br />
* meta.xml<br />
* mimetype<br />
* settings.xml<br />
* styles.xml<br />
<br />
===Inner files description===<br />
====manifest.xml====<br />
Lists all the other xml files that are in this document. In the event of the simple document its contents maybe something like:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 1.0//EN" "Manifest.dtd"><br />
<manifest:manifest xmlns:manifest="urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"><br />
<manifest:file-entry manifest:media-type="application/vnd.oasis.opendocument.text" manifest:full-path="/"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="content.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="styles.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="meta.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="settings.xml"/><br />
</manifest:manifest><br />
<br />
====content.xml====<br />
This is the file that contains all the text in the document.<br />
<br />
The root element is always &lt;office:document-content&gt;. To get the text without metadata you go through the following hierarchy:<br />
* office:document-content<br />
** office:body<br />
*** office:text<br />
<br />
There you will find tags in the ''text'' namespace, that either mirror HTML in their names or are self-explanatory for the most part. Some examplese are:<br />
* text:p - paragraph<br />
* text:list - a listing that will have several text:list-item elements<br />
* text:list-item - a single item of the list<br />
<br />
Each text tag may have text:style attribute that links it to the style that is defined in office:document-content > office:automatic-styles > style:style.<br />
<br />
====manifest.rdf====<br />
[[RDF]] metadata. Most often the contents are just<br />
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
</rdf:RDF><br />
<br />
====meta.xml====<br />
This is the metadata that somebody fills in to describe the document or is automatically recorded by the software. The root element is always office:document-meta. The contents are defined rather loosely, the editing software is advised not to delete tags that it doesn't recognise, since other software maybe using them. In practice deleting all the contents of office:document-meta > office:meta will not damage the document, and it can be considered non-essential information.<br />
<br />
====mimetype====<br />
A text file that consists of<br />
application/vnd.oasis.opendocument.text<br />
<br />
====settings.xml====<br />
Software specific settings of the document. The root tag is &lt;office:document-settings&gt;. No inner contents are required for the functioning document.<br />
<br />
====styles.xml====<br />
Non-automatic document styles, that are held in &lt;office:document-styles&gt; tag.<br />
<br />
== Microsoft Office 2010 ==<br />
<br />
Microsoft Office 2010 seems to have some issues adhering to the OpenDocument standard. See the following link for more information;<br />
<br />
* [http://tbullock.comlore.com/2011/04/odf-12-support-in-microsoft-office.html Depth of Knowledge: ODF 1.2 Support in Microsoft Office]<br />
<br />
== Sample files ==<br />
* [http://www.dan.info/sampledata/msword/testing.odt Sample document saved from Windows Word 2007]<br />
<br />
== Links ==<br />
* [http://blog.riemann.cc/2013/04/23/versioning-of-openoffice-libreoffice-documents-using-git/ Versioning of OpenOffice/LibreOffice Documents Using Git]<br />
* [http://wiki.opf-labs.org/display/TR/OpenDocument+Text OpenDocument Text entries in OPF File Format Risk Registry ]<br />
* [https://updegrove.wordpress.com/2014/03/12/odf-vs-ooxml-war-of-the-words/ ODF vs. OOXML: War of the Words]<br />
* [http://askubuntu.com/questions/60778/how-can-i-convert-an-odt-file-to-a-pdf How to convert ODT to PDF]<br />
<br />
[[Category:XML based file formats]]<br />
[[Category:ZIP based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/OpenDocument_TextOpenDocument Text2015-07-19T21:12:18Z<p>SwanQ: /* Image embedding issue */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Document<br />
|extensions={{ext|fodt}}, {{ext|odt}}<br />
|mimetypes={{mimetype|application/vnd.oasis.opendocument.text}}<br />
|pronom={{PRONOM|fmt/136}},{{PRONOM|fmt/290}},{{PRONOM|fmt/291}}<br />
|released=2005-05-01<br />
}}<br />
The '''OpenDocument Text''' format is one of a number of types of the [[OpenDocument|Open Document Format for Office Applications]] (commonly referred to as OpenDocument), an [[XML]]-based file format defined by the Organization for the Advancement of Structured Information Standards (OASIS) in 2005.<br />
<br />
OpenDocument Text can, like all [[OpenDocument]] files, be represented in one of two fashions - as a single XML document or as a collection of several sub-documents within a single package (commonly a [[ZIP]] archive). Generally, the extension '''.fodt''' is used for the uncommonly-used single XML documents and '''.odt''' for packaged sub-documents.<br />
<br />
== Image embedding issue ==<br />
Both OpenOffice and LibreOffice are affected by a long-running bug where upon pasting an image into a document, only a ''hyperlink'' to the image is inserted by default (rather than the ''actual image data''). More details can be found [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice here]. This bug was first reported in 2004, and as of 2013 it still hasn't been resolved. It was apparently fixed in LibreOffice in early 2014 [http://wiki.opf-labs.org/display/TR/Images+not+embedded+because+of+paste+as+link+bug+in+OpenOffice+and+LibreOffice].<br />
<br />
== Information ==<br />
<br />
* [https://www.oasis-open.org/standards#opendocumentv1.0 OpenDocument v1.0 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.1 OpenDocument v1.1 specification]<br />
* [https://www.oasis-open.org/standards#opendocumentv1.2 OpenDocument v1.2 specification]<br />
* [http://en.wikipedia.org/wiki/OpenDocument Wikipedia - OpenDocument]<br />
<br />
== Zipped Archive Structure ==<br />
<br />
When stored as a ZIP archive (with an .odt extension), it contains [[XML]] files describing text and relationships and [[JPEG]], [[PNG]], and other graphical files for pictures and other media included in the document.<br />
<br />
The layout of the regular ODT file is the following:<br />
* META-INF<br />
** manifest.xml<br />
* Thumbnails<br />
** thumbnail.png<br />
* content.xml<br />
* manifest.rdf<br />
* meta.xml<br />
* mimetype<br />
* settings.xml<br />
* styles.xml<br />
<br />
===Inner files description===<br />
====manifest.xml====<br />
Lists all the other xml files that are in this document. In the event of the simple document its contents maybe something like:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 1.0//EN" "Manifest.dtd"><br />
<manifest:manifest xmlns:manifest="urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"><br />
<manifest:file-entry manifest:media-type="application/vnd.oasis.opendocument.text" manifest:full-path="/"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="content.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="styles.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="meta.xml"/><br />
<manifest:file-entry manifest:media-type="text/xml" manifest:full-path="settings.xml"/><br />
</manifest:manifest><br />
<br />
====content.xml====<br />
This is the file that contains all the text in the document.<br />
<br />
The root element is always &lt;office:document-content&gt;. To get the text without metadata you go through the following hierarchy:<br />
* office:document-content<br />
** office:body<br />
*** office:text<br />
<br />
There you will find tags in the ''text'' namespace, that either mirror HTML in their names or are self-explanatory for the most part. Some examplese are:<br />
* text:p - paragraph<br />
* text:list - a listing that will have several text:list-item elements<br />
* text:list-item - a single item of the list<br />
<br />
Each text tag may have text:style attribute that links it to the style that is defined in office:document-content > office:automatic-styles > style:style.<br />
<br />
====manifest.rdf====<br />
[[RDF]] metadata. Most often the contents are just<br />
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
</rdf:RDF><br />
<br />
====meta.xml====<br />
This is the metadata that somebody fills in to describe the document or is automatically recorded by the software. The root element is always office:document-meta. The contents are defined rather loosely, the editing software is advised not to delete tags that it doesn't recognise, since other software maybe using them. In practice deleting all the contents of office:document-meta > office:meta will not damage the document, and it can be considered non-essential information.<br />
<br />
====mimetype====<br />
A text file that consists of<br />
application/vnd.oasis.opendocument.text<br />
<br />
====settings.xml====<br />
Software specific settings of the document. The root tag is &lt;office:document-settings&gt;. No inner contents are required for the functioning document.<br />
<br />
====styles.xml====<br />
Non-automatic document styles, that are held in &lt;office:document-styles&gt; tag.<br />
<br />
== Microsoft Office 2010 ==<br />
<br />
Microsoft Office 2010 seems to have some issues adhering to the OpenDocument standard. See the following link for more information;<br />
<br />
* [http://tbullock.comlore.com/2011/04/odf-12-support-in-microsoft-office.html Depth of Knowledge: ODF 1.2 Support in Microsoft Office]<br />
<br />
== Sample files ==<br />
* [http://www.dan.info/sampledata/msword/testing.odt Sample document saved from Windows Word 2007]<br />
<br />
== Links ==<br />
* [http://blog.riemann.cc/2013/04/23/versioning-of-openoffice-libreoffice-documents-using-git/ Versioning of OpenOffice/LibreOffice Documents Using Git]<br />
* [http://wiki.opf-labs.org/display/TR/OpenDocument+Text OpenDocument Text entries in OPF File Format Risk Registry ]<br />
* [https://updegrove.wordpress.com/2014/03/12/odf-vs-ooxml-war-of-the-words/ ODF vs. OOXML: War of the Words]<br />
* [http://askubuntu.com/questions/60778/how-can-i-convert-an-odt-file-to-a-pdf How to convert ODT to PDF]<br />
<br />
[[Category:XML based file formats]]<br />
[[Category:ZIP based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GMLJP2GMLJP22015-01-26T19:32:18Z<p>SwanQ: /* Format */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|subcat2=JPEG 2000<br />
|extensions={{ext|jpf}}, {{ext|jpx}}<br />
|mimetypes={{mimetype|image/jpx}}<br />
|locfdd={{LoCFDD|fdd000303}}<br />
}}<br />
'''GMLJP2''' is a metadata standard that enables one to embed geospatial<br />
metadata in georeferenced [[JPX]] ([[JPEG 2000]] Part 2) images.<br />
<br />
== Format ==<br />
GMLJP2 data is [[XML]]-based, and is stored in "<code>xml&nbsp;</code>" boxes nested inside "<code>asoc</code>" boxes.<br />
<br />
Because "<code>asoc</code>" boxes are only defined in the JPX specification, and not in the JP2 specification, GMLJP2 files must be labeled (branded) as JPX format instead of [[JP2]] format. However, some invalid GMLJP2 files labeled as JP2 do exist.<br />
<br />
Version 1.0 was approved on January 20, 2006. Version 2.0 was approved by OGC on June 30, 2014.<br />
<br />
== See also ==<br />
* [[GeoJP2]] is an alternative standard for embedding geospatial metadata in [[JPEG 2000]] images which is based on the [[GeoTIFF]] format.<br />
<br />
== Specifications ==<br />
* [http://www.opengeospatial.org/standards/gmljp2 GML in JPEG 2000 for Geographic Imagery Encoding], now known as Version 1.0<br />
* [http://docs.opengeospatial.org/is/08-085r4/08-085r4.html OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core], known as Version 2.0<br />
<br />
[[Category:Graphics]]<br />
[[Category:XML based file formats]]<br />
[[Category:JPEG 2000]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GMLJP2GMLJP22015-01-26T19:29:35Z<p>SwanQ: /* Format */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|subcat2=JPEG 2000<br />
|extensions={{ext|jpf}}, {{ext|jpx}}<br />
|mimetypes={{mimetype|image/jpx}}<br />
|locfdd={{LoCFDD|fdd000303}}<br />
}}<br />
'''GMLJP2''' is a metadata standard that enables one to embed geospatial<br />
metadata in georeferenced [[JPX]] ([[JPEG 2000]] Part 2) images.<br />
<br />
== Format ==<br />
GMLJP2 data is [[XML]]-based, and is stored in "<code>xml&nbsp;</code>" boxes nested inside "<code>asoc</code>" boxes.<br />
<br />
Because "<code>asoc</code>" boxes are only defined in the JPX specification, and not in the JP2 specification, GMLJP2 files must be labeled (branded) as JPX format instead of [[JP2]] format. However, some invalid GMLJP2 files labeled as JP2 do exist.<br />
<br />
Version 1.0 was approved in 2006. Version 2.0 was approved by OGC on June 30, 2014.<br />
<br />
== See also ==<br />
* [[GeoJP2]] is an alternative standard for embedding geospatial metadata in [[JPEG 2000]] images which is based on the [[GeoTIFF]] format.<br />
<br />
== Specifications ==<br />
* [http://www.opengeospatial.org/standards/gmljp2 GML in JPEG 2000 for Geographic Imagery Encoding], now known as Version 1.0<br />
* [http://docs.opengeospatial.org/is/08-085r4/08-085r4.html OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core], known as Version 2.0<br />
<br />
[[Category:Graphics]]<br />
[[Category:XML based file formats]]<br />
[[Category:JPEG 2000]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GMLJP2GMLJP22015-01-26T19:28:13Z<p>SwanQ: /* Specifications */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|subcat2=JPEG 2000<br />
|extensions={{ext|jpf}}, {{ext|jpx}}<br />
|mimetypes={{mimetype|image/jpx}}<br />
|locfdd={{LoCFDD|fdd000303}}<br />
}}<br />
'''GMLJP2''' is a metadata standard that enables one to embed geospatial<br />
metadata in georeferenced [[JPX]] ([[JPEG 2000]] Part 2) images.<br />
<br />
== Format ==<br />
GMLJP2 data is [[XML]]-based, and is stored in "<code>xml&nbsp;</code>" boxes nested inside "<code>asoc</code>" boxes.<br />
<br />
Because "<code>asoc</code>" boxes are only defined in the JPX specification, and not in the JP2 specification, GMLJP2 files must be labeled (branded) as JPX format instead of [[JP2]] format. However, some invalid GMLJP2 files labeled as JP2 do exist.<br />
<br />
== See also ==<br />
* [[GeoJP2]] is an alternative standard for embedding geospatial metadata in [[JPEG 2000]] images which is based on the [[GeoTIFF]] format.<br />
<br />
== Specifications ==<br />
* [http://www.opengeospatial.org/standards/gmljp2 GML in JPEG 2000 for Geographic Imagery Encoding], now known as Version 1.0<br />
* [http://docs.opengeospatial.org/is/08-085r4/08-085r4.html OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core], known as Version 2.0<br />
<br />
[[Category:Graphics]]<br />
[[Category:XML based file formats]]<br />
[[Category:JPEG 2000]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GMLJP2GMLJP22015-01-26T19:27:52Z<p>SwanQ: /* Specifications */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|subcat2=JPEG 2000<br />
|extensions={{ext|jpf}}, {{ext|jpx}}<br />
|mimetypes={{mimetype|image/jpx}}<br />
|locfdd={{LoCFDD|fdd000303}}<br />
}}<br />
'''GMLJP2''' is a metadata standard that enables one to embed geospatial<br />
metadata in georeferenced [[JPX]] ([[JPEG 2000]] Part 2) images.<br />
<br />
== Format ==<br />
GMLJP2 data is [[XML]]-based, and is stored in "<code>xml&nbsp;</code>" boxes nested inside "<code>asoc</code>" boxes.<br />
<br />
Because "<code>asoc</code>" boxes are only defined in the JPX specification, and not in the JP2 specification, GMLJP2 files must be labeled (branded) as JPX format instead of [[JP2]] format. However, some invalid GMLJP2 files labeled as JP2 do exist.<br />
<br />
== See also ==<br />
* [[GeoJP2]] is an alternative standard for embedding geospatial metadata in [[JPEG 2000]] images which is based on the [[GeoTIFF]] format.<br />
<br />
== Specifications ==<br />
* [http://www.opengeospatial.org/standards/gmljp2 GML in JPEG 2000 for Geographic Imagery Encoding], now known as Version 1.0<br />
* [http://docs.opengeospatial.org/is/08-085r4/08-085r4.html OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core], known as Version 2<br />
<br />
[[Category:Graphics]]<br />
[[Category:XML based file formats]]<br />
[[Category:JPEG 2000]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/BigTIFFBigTIFF2015-01-25T18:25:39Z<p>SwanQ: /* Software */ added link to software fork for libtiff</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|tif}} {{ext|tiff}}<br />
|locfdd={{LoCFDD|fdd000328}}<br />
}}<br />
== Overview ==<br />
'''BigTIFF''' is a [[TIFF]]-like image file format, which supports larger files and data structures than does TIFF. It is logically almost identical to TIFF, though it is not compatible with it.<br />
<br />
== Identification ==<br />
Files begin with <code>49 49 2B 00 08 00 00 00</code> (little-endian BigTIFF), or <code>4D 4D 00 2B 00 08 00 00</code> (big-endian BigTIFF).<br />
<br />
== Software ==<br />
* [http://www.remotesensing.org/libtiff/ LibTIFF], starting with version 4.<br />
* [http://bigtiff.org/ Fork of libtiff], apparently unofficial fork of libtiff which originated with Aperio, now part of Leica Biosystems.<br />
<br />
== Sample files ==<br />
* ftp://ftp.graphicsmagick.org/pub/tiff-samples/<br />
* http://awaresystems.be/imaging/tiff/bigtiff/BigTIFFSamples.zip<br />
<br />
== External links ==<br />
* [http://www.awaresystems.be/imaging/tiff/bigtiff.html AWare Systems BigTIFF page]<br />
* [http://www.remotesensing.org/libtiff/bigtiffpr.html BigTIFF Proposal]<br />
<br />
[[Category:TIFF]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/KMLKML2015-01-25T18:03:55Z<p>SwanQ: Added locfdd id</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|extensions={{ext|kml}} {{ext|kmz}}<br />
|mimetypes={{mimetype|application/vnd.google-earth.kml+xml}}, {{mimetype|application/vnd.google-earth.kmz}}<br />
|locfdd={{LoCFDD|fdd000340}}<br />
|pronom={{PRONOM|fmt/244}}<br />
|released=2008<br />
}}<br />
<br />
'''[[KML]]''' is derived from Keyhole Markup Language. KML is an [[XML]] notation for geographic annotation and visualization of features for use in two-dimensional maps and three-dimensional Earth browsers used on the Internet. The KML file specifies a set of features (place marks, images, polygons, 3D models, textual descriptions, etc.) for display in applications such as Google Earth and Google Maps or any other geospatial software implementing the KML encoding. Positions are located using longitude and latitude as defined by the World Geodetic System of 1984 (WGS84). KML became an international standard of the Open Geospatial Consortium in 2008.<br />
<br />
KMZ files are KML files that are compressed in the [[ZIP]] format (in compatibility mode for ZIP 2.0).<br />
<br />
== References ==<br />
* [http://www.opengeospatial.org/standards/kml/ KML specification from OGC]<br />
* [http://schemas.opengis.net/kml/ KML schemas from OGC]<br />
* [https://developers.google.com/kml/documentation/ KML documentation and examples from Google]<br />
* [http://en.wikipedia.org/wiki/Keyhole_Markup_Language Keyhole Markup Language : Wikipedia]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000340.shtml KML, Version 2.2, from Library of Congress resource on Sustainability of Digital Formats]<br />
<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/ZIPZIP2013-09-16T19:32:31Z<p>SwanQ: /* References */</p>
<hr />
<div>:''Not to be confused with [[Zip disk]], an unrelated disk cartridge unit.''<br />
{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Archiving<br />
|extensions={{ext|zip}}<br />
|mimetypes={{mimetype|application/zip}}<br />
|pronom={{PRONOM|x-fmt/263}}<br />
|released=1989<br />
}}<br />
<br />
'''ZIP''' is one of the most popular file compression formats. It was created in 1989 as the native format of the PKZIP program, which was introduced by Phil Katz in the wake of a lawsuit (which he lost) against him by the makers of the then-popular [[ARC]] program (and file format) for copyright and trademark infringement in an earlier program PKARC which had been file-compatible with ARC. This resulted in Katz creating a new file format, which rapidly overtook ARC in popularity (to a large extent because of BBS sysops, then the primary users of such compression, resenting the lawsuit). Many programs have been released for a variety of operating systems to compress and decompress ZIP files, and native support for the format is built into several popular operating systems.<br />
<br />
ZIP implementations vary in their support for features in the specification from PKWARE (http://www.pkware.com/documents/casestudies/APPNOTE.TXT), particularly features added since version 2 (1993), some of which are protected by patents and require licensing. Many implementations limit the use of compression to the [[DEFLATE]] algorithm, introduced with version 2. Extensions incorporated into the specification that have been widely adopted are: long filenames; large files (using a technique known as ZIP64); and filenames in UTF-8. In 2011 work began on an interoperable subset of the latest APPNOTE.TXT with the intention of publication as ISO/IEC 21320-1, Document Container File -- Part 1: Core. As of November 2012, a discussion draft is available at http://www.itscj.ipsj.or.jp/sc34/open/1855.pdf. Designed to promote interoperable implementations, the draft ISO/IEC 21320-1 prohibits compression other than using [[DEFLATE]], segmentation or multiple volumes, and features that are subject to patents.<br />
<br />
While .zip is the usual file extension, ZIP-formatted files can be found with many other extensions since a number of other file formats use ZIP compression but store their files in application-specific extensions.<br />
<br />
== Identifiers ==<br />
* File extension: '''.ZIP'''<br />
* MIME type (Internet media type): '''application/zip'''<br />
* Uniform Type Identifier (Apple): '''com.pkware.zip-archive'''<br />
* PUID (PRONOM): '''x-fmt/263'''<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/ZIP_%28file_format%29 ZIP (file format): Wikipedia]<br />
* [http://www.pkware.com/documents/casestudies/APPNOTE.TXT APPNOTE from PKWARE] (latest version of formal spec)<br />
* [http://www.pkware.com/support/zip-app-note/archives APPNOTE Archives from PKWARE] (selected versions since 4.5.0 from 2001)<br />
* [http://www.iana.org/assignments/media-types/application/zip IANA registration for application/zip in July 1993] (corresponds to version 2 of APPNOTE.TXT)<br />
* [ftp://ftp.info-zip.org/pub/infozip/doc/ Documentation from Info-ZIP] (Includes Info-ZIP variants on APPNOTE.TXT dated from 1996 to 2004, specifications used as the basis for various open-source tools)<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000354.shtml ZIP File Format (PKWARE), from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://www.nationalarchives.gov.uk/PRONOM/x-fmt/263 ZIP Format summary at PRONOM]<br />
* [http://www.itscj.ipsj.or.jp/sc34/open/1855.pdf November 2012 working draft of ISO/IEC WD 21320-1, Document Container File -- Part 1: Core] Intended as restricted subset of APPNOTE 6.3.3 designed to promote interoperability.<br />
* [http://www.itscj.ipsj.or.jp/sc34/open/1886.pdf February 2013 committee draft of ISO/IEC CD 21320-1, Document Container File -- Part 1: Core] Essentially the same as November 2012 working draft except that it mandates use of the UTF-8 indicator.<br />
* [http://apple2.org.za/gswv/a2zine/GS.WorldView/Resources/The.MacShrinkIt.Project/ARCHIVES.TXT Archive format info, including ZIP] (from 1989, when ZIP was newly released)</div>SwanQhttp://fileformats.archiveteam.org/wiki/BWFBWF2013-03-13T07:07:38Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|subcat=Audio and Music<br />
|extensions={{ext|wav}}<br />
|mimetypes={{mimetype|audio/x-wav}}<br />
|pronom={{PRONOM|fmt/2}}<br />
|locfdd={{LoCFDD|fdd000356}}<br>{{LoCFDD|fdd000357}}<br />
}}<br />
<br />
'''BWF''' is used for broadcast exchange and as an archival format for first-generation (master) audio files. [[BWF]] extends the [[WAV]] standard with a mandatory metadata chunk and restricts the audio datastream to Linear PCM ([[LPCM]]) or MPEG forms.<br />
<br />
== References ==<br />
* [http://tech.ebu.ch/docs/tech/tech3285.pdf EBU TECH 3285: Specification of the Broadcast Wave Format (BWF)]<br />
* [http://en.wikipedia.org/wiki/Broadcast_Wave_Format Broadcast Wave Format : Wikipedia]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000356.shtml Broadcast WAVE Audio File Format, Version 1, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/TIFF/EPTIFF/EP2013-03-13T06:45:57Z<p>SwanQ: </p>
<hr />
<div>{|<br />
|[[File Formats]]<br />
| ><br />
|[[Electronic File Formats]]<br />
| ><br />
|[[Graphics]]<br />
| ><br />
|[[TIFF/EP]]<br />
|}<br />
<br />
{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|tiff}}, {{ext|tif}}<br />
|pronom={{PRONOM|fmt/154}}<br />
|locfdd={{LoCFDD|fdd000073}}<br />
}}<br />
<br />
[[TIFF/EP]] is a subtype of [[TIFF]] developed as an ISO standard for electronic photography, ISO 12234-2, titled "Electronic still-picture imaging – Removable memory – Part 2: TIFF/EP image data format." The TIFF/EP is based on a subset of [[TIFF]] and a subset of the JEITA Exif standard, with some differences and extensions. The 2001 standard has not been adopted per se by most camera manufacturers, although some proprietary ''raw'' formats and the [[DNG]] format claim to be compatible with TIFF/EP/.<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/TIFF/EP TIFF/EP : Wikipedia]<br />
<br />
[[Category:TIFF]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/DNGDNG2013-03-13T06:41:14Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Cameras and Digital Image Sensors<br />
|extensions={{ext|dng}}<br />
|pronom={{PRONOM|fmt/436}}<br>{{PRONOM|fmt/152}}<br>{{PRONOM|fmt/437}}<br>{{PRONOM|fmt/438}}<br />
|locfdd={{LoCFDD|fdd000188}}<br />
}}<br />
'''Digital Negative''' ('''DNG''') is a digital camera raw image format developed by Adobe. DNG is an extension of [[TIFF]] 6.0 and is compatible with [[TIFF/EP]].<br />
<br />
== Specifications ==<br />
<br />
* [http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf Digital Negative Specification, Version 1.4.0.0] (2012-06)<br />
* [http://web.archive.org/web/20100525075805/http://www.adobe.com/products/dng/pdfs/dng_spec_1_3_0_0.pdf Digital Negative Specification, Version 1.3.0.0] (2009-06)<br />
* [http://web.archive.org/web/20090521113533/http://www.adobe.com/products/dng/pdfs/dng_spec_1_2_0_0.pdf Digital Negative Specification, Version 1.2.0.0] (2008-04)<br />
* [http://web.archive.org/web/20070323050148/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.1.0.0] (2005-02)<br />
* [http://web.archive.org/web/20041204034106/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.0.0.0] (2004-09)<br />
<br />
== See also ==<br />
<br />
* [[TIFF/EP]]<br />
* [[CinemaDNG]]<br />
<br />
== External links ==<br />
<br />
* [[Wikipedia:Digital Negative]]<br />
* [http://www.adobe.com/products/photoshop/extend.displayTab2.html DNG resources from Adobe]<br />
* [http://www.barrypearson.co.uk/articles/dng/index.htm Barry Pearson's DNG articles and links]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000188.shtml Adobe Digital Negative (DNG), Version 1.1, from Library of Congress resource on Sustainability of Digital Formats]<br />
<br />
[[Category:TIFF]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/LPCMLPCM2013-03-13T06:36:31Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Audio and Music<br />
|locfdd={{LoCFDD|fdd000011}}<br />
}}<br />
<br />
'''[[LPCM]]''' stands for Linear Pulse Code Modulation, also referred to as Linear PCM. It is a digital audio encoding, using pulse code modulation (PCM) with linear quantization. PCM is a digital representation of an analog signal where the magnitude of the signal is sampled regularly at uniform intervals, then quantized to a series of symbols in a digital (usually binary) code. PCM has been used in digital telephone systems and [[LPCM]] is the standard form for digital audio on audio compact disks.<br />
<br />
LPCM encoding is the default audio encoding for the Broadcast Wave Format ([[BWF]]), [[WAV]] and [[AIFF]]. It is one of the audio encodings permitted in [[Matroska]].<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/Linear_pulse_code_modulation LPCM (file format): Wikipedia]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000011.shtml Linear Pulse Code Modulated Audio (LPCM), from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/DNGDNG2013-03-13T05:50:51Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Cameras and Digital Image Sensors<br />
|extensions={{ext|dng}}<br />
|pronom={{PRONOM|fmt/152}}<br />
}}<br />
'''Digital Negative''' ('''DNG''') is a digital camera raw image format developed by Adobe. DNG is an extension of [[TIFF]] 6.0 and is compatible with [[TIFF/EP]].<br />
<br />
== Specifications ==<br />
<br />
* [http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf Digital Negative Specification, Version 1.4.0.0] (2012-06)<br />
* [http://web.archive.org/web/20100525075805/http://www.adobe.com/products/dng/pdfs/dng_spec_1_3_0_0.pdf Digital Negative Specification, Version 1.3.0.0] (2009-06)<br />
* [http://web.archive.org/web/20090521113533/http://www.adobe.com/products/dng/pdfs/dng_spec_1_2_0_0.pdf Digital Negative Specification, Version 1.2.0.0] (2008-04)<br />
* [http://web.archive.org/web/20070323050148/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.1.0.0] (2005-02)<br />
* [http://web.archive.org/web/20041204034106/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.0.0.0] (2004-09)<br />
<br />
== See also ==<br />
<br />
* [[TIFF/EP]]<br />
* [[CinemaDNG]]<br />
<br />
== External links ==<br />
<br />
* [[Wikipedia:Digital Negative]]<br />
* [http://www.adobe.com/products/photoshop/extend.displayTab2.html DNG resources from Adobe]<br />
* [http://www.barrypearson.co.uk/articles/dng/index.htm Barry Pearson's DNG articles and links]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000188.shtml Adobe Digital Negative (DNG), Version 1.1, from Library of Congress resource on Sustainability of Digital Formats]<br />
<br />
[[Category:TIFF]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/DNGDNG2013-03-13T05:46:06Z<p>SwanQ: /* External links */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Cameras and Digital Image Sensors<br />
|extensions={{ext|dng}}<br />
}}<br />
'''Digital Negative''' ('''DNG''') is a digital camera raw image format developed by Adobe. DNG is an extension of [[TIFF]] 6.0 and is compatible with [[TIFF/EP]].<br />
<br />
== Specifications ==<br />
<br />
* [http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf Digital Negative Specification, Version 1.4.0.0] (2012-06)<br />
* [http://web.archive.org/web/20100525075805/http://www.adobe.com/products/dng/pdfs/dng_spec_1_3_0_0.pdf Digital Negative Specification, Version 1.3.0.0] (2009-06)<br />
* [http://web.archive.org/web/20090521113533/http://www.adobe.com/products/dng/pdfs/dng_spec_1_2_0_0.pdf Digital Negative Specification, Version 1.2.0.0] (2008-04)<br />
* [http://web.archive.org/web/20070323050148/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.1.0.0] (2005-02)<br />
* [http://web.archive.org/web/20041204034106/http://www.adobe.com/products/dng/pdfs/dng_spec.pdf Digital Negative Specification, Version 1.0.0.0] (2004-09)<br />
<br />
== See also ==<br />
<br />
* [[TIFF/EP]]<br />
* [[CinemaDNG]]<br />
<br />
== External links ==<br />
<br />
* [[Wikipedia:Digital Negative]]<br />
* [http://www.adobe.com/products/photoshop/extend.displayTab2.html DNG resources from Adobe]<br />
* [http://www.barrypearson.co.uk/articles/dng/index.htm Barry Pearson's DNG articles and links]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000188.shtml Adobe Digital Negative (DNG), Version 1.1, from Library of Congress resource on Sustainability of Digital Formats]<br />
<br />
[[Category:TIFF]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/EADEAD2013-01-13T02:56:25Z<p>SwanQ: corrected extension</p>
<hr />
<div>{{FormatInfo<br />
|subcat=Bibliographic data<br />
|extensions={{ext|xml}}<br />
}}<br />
<br />
An '''Encoded Archival Description''' is a standardized, structured document, often referred to as a ''finding aid'', for describing archival collections, such as the personal papers of noteworthy individuals. Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials.<br />
<br />
The first EAD specification was based on [[SGML]] and was released in an alpha version in February 1996. The DTD was converted to [[XML]] in 1998. Schemas in XML Schema Language and RNG (Relax NG) were released for an updated EAD specification, published in 2002. EAD's developers incorporated significant concepts from the international descriptive framework provided by the General International Standard Archival Description (ISAD(G) and from national descriptive content standards such as the Canadian Rules for Archival Description (RAD). <br />
<br />
== Specifications ==<br />
* [http://www.loc.gov/ead/ead.rng EAD 2002 (Schema as RNG)]<br />
* [http://www.loc.gov/ead/ead.xsd EAD 2002 (Schema as XSD)]<br />
<br />
== References ==<br />
* [http://www.loc.gov/ead/ EAD official site]<br />
<br />
== Sample files ==<br />
*[http://findingaids.loc.gov/source/MSS_A Finding aids at the Library of Congress]</div>SwanQhttp://fileformats.archiveteam.org/wiki/EADEAD2013-01-13T02:22:35Z<p>SwanQ: Created page with "{{FormatInfo |subcat=Bibliographic data |extensions={{ext|dcx}} }} An '''Encoded Archival Description''' is a standardized, structured document, often referred to as a ''find..."</p>
<hr />
<div>{{FormatInfo<br />
|subcat=Bibliographic data<br />
|extensions={{ext|dcx}}<br />
}}<br />
<br />
An '''Encoded Archival Description''' is a standardized, structured document, often referred to as a ''finding aid'', for describing archival collections, such as the personal papers of noteworthy individuals. Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials.<br />
<br />
The first EAD specification was based on [[SGML]] and was released in an alpha version in February 1996. The DTD was converted to [[XML]] in 1998. Schemas in XML Schema Language and RNG (Relax NG) were released for an updated EAD specification, published in 2002. EAD's developers incorporated significant concepts from the international descriptive framework provided by the General International Standard Archival Description (ISAD(G) and from national descriptive content standards such as the Canadian Rules for Archival Description (RAD). <br />
<br />
== Specifications ==<br />
* [http://www.loc.gov/ead/ead.rng EAD 2002 (Schema as RNG)]<br />
* [http://www.loc.gov/ead/ead.xsd EAD 2002 (Schema as XSD)]<br />
<br />
== References ==<br />
* [http://www.loc.gov/ead/ EAD official site]</div>SwanQhttp://fileformats.archiveteam.org/wiki/Dublin_CoreDublin Core2013-01-13T01:56:06Z<p>SwanQ: /* References */</p>
<hr />
<div>{{FormatInfo<br />
|subcat=Bibliographic data<br />
|extensions={{ext|dcx}}<br />
}}<br />
<br />
The '''Dublin Core''' (which has nothing to do with Ireland; the Dublin referred to is Dublin, Ohio, USA, where the first meeting was held to devise the standard) is a standardized set of metadata fields to give information about resources. Its uses include as meta tags in [[HTML]] to identify web documents, but there is also an [[XML]]-based standalone format for it which can be used for storing bibliographic information.<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/Dublin_Core Dublin Core (Wikipedia)]<br />
* [http://dublincore.org/ Dublin Core official site]<br />
* [http://www.dublincoregenerator.com/ Dublin Core Generator] (online utility)</div>SwanQhttp://fileformats.archiveteam.org/wiki/Dublin_CoreDublin Core2013-01-13T01:55:20Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|subcat=Bibliographic data<br />
|extensions={{ext|dcx}}<br />
}}<br />
<br />
The '''Dublin Core''' (which has nothing to do with Ireland; the Dublin referred to is Dublin, Ohio, USA, where the first meeting was held to devise the standard) is a standardized set of metadata fields to give information about resources. Its uses include as meta tags in [[HTML]] to identify web documents, but there is also an [[XML]]-based standalone format for it which can be used for storing bibliographic information.<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/Dublin_Core Dublin core (Wikipedia)]<br />
* [http://dublincore.org/ Dublin Core official site]<br />
* [http://www.dublincoregenerator.com/ Dublin Core Generator] (online utility)</div>SwanQhttp://fileformats.archiveteam.org/wiki/WebWeb2013-01-13T01:51:09Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|thiscat=Web<br />
|released=1990<br />
}}<br />
<br />
* [[ActiveX]]<br />
* [[Atom]] (syndication format)<br />
* [[BBCode]]<br />
* [[Cascading Style Sheets]] (CSS)<br />
* [[Common Gateway Interface]] (CGI)<br />
* [[Domain names]]<br />
* [[Favicon]]<br />
* [[HTML|HTML/XHTML]]<br />
* [[HTTP]]<br />
* [[Internet Shortcut]]<br />
* [[JavaScript]] / [[ECMAScript]]<br />
* [[Markdown]]<br />
* [[Mime-type]]<br />
* [[Open Web App Manifest]] (.webapp)<br />
* [[RDF]]<br />
* [[RSS]]<br />
* [[Robots Exclusion Standard]] (robots.txt)<br />
* [[URLs]] (and URIs, URNs, etc.)<br />
* [[URL shorteners]]<br />
* [[VBScript]]<br />
* [[webarchive]] (HTML packaging format used by Apple Safari)<br />
* [[Web browser files]] (bookmarks, cookies, configurations, etc.)<br />
* [[Web server files]] (server configuration, etc.)<br />
* [[Wiki markup]]<br />
* [[WOFF]]<br />
<br />
See also [[E-Mail, newsgroups, and forums]] (a number of web-based messaging/social-networking things are there)</div>SwanQhttp://fileformats.archiveteam.org/wiki/RDFRDF2013-01-13T01:49:02Z<p>SwanQ: Added link for RFC 3870</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Web<br />
|extensions={{ext|rdf}}<br />
|mimetypes={{mimetype|application/rdf+xml}}<br />
|released=1999<br />
}}<br />
<br />
'''RDF''' (Resource Description Framework) is a W3C standard describing both an abstract structure for keeping track of information about a resource, and the concrete implementation of this structure serialized as an [[XML]] document.<br />
<br />
RDF was originally the basis of the [[RSS]] standard, though some later versions of RSS (though not all, due to its forked development with different philosophies of different developers) are no longer based on RDF.<br />
<br />
RDF can be used to express metadata about a particular thing and its relationships with other things. It is an important element of the Semantic Web project, intending to evolve the Web to a stage where it enables automatic processing of information in a rigorously-defined way.<br />
<br />
== Standards ==<br />
* [http://www.w3.org/TR/2004/REC-rdf-schema-20040210/ W3C: RDF Vocabulary Description Language 1.0: RDF Schema (2004)]<br />
* [http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/ W3C: RDF/XML Syntax Specification (2004)]<br />
* [http://www.ietf.org/rfc/rfc3870.txt RFC 3870] (MIME type registration)<br />
<br />
== Other links ==<br />
* [http://www.w3.org/RDF/ W3C RDF page]<br />
* [[Wikipedia:Resource Description Framework|Wikipedia article]]<br />
<br />
[[Category:XML based file formats]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GeospatialGeospatial2013-01-13T01:29:03Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|thiscat=Geospatial<br />
}}<br />
<br />
== Cross reference ==<br />
See also [[Scientific Data formats#Geographic_and_Geospatial|the Scientific Data formats section]].<br />
<br />
== Raster Formats ==<br />
<br />
* [[GeoTIFF]]<br />
* [[MrSID]]<br />
* [[PCRaster Map]]<br />
<br />
== Vector Formats ==<br />
* [[Shapefile]]<br />
* [[KML]]<br />
* [[E00]] -- ArcInfo interchange file<br />
<br />
== Grid Formats -- see also raster formats, above ==<br />
* [[DEM]]<br />
<br />
== Point cloud ==<br />
* [[LAS]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/GeospatialGeospatial2013-01-13T01:28:30Z<p>SwanQ: /* Grid Formats -- see raster formats, above */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|thiscat=Geospatial<br />
}}<br />
<br />
== Cross reference ==<br />
See also [[Scientific Data formats#Geographic_and_Geospatial|the Scientific Data formats section]].<br />
<br />
== Raster Formats ==<br />
<br />
* [[GeoTIFF]]<br />
* [[MrSID]]<br />
* [[PCRaster Map]]<br />
<br />
== Vector Formats ==<br />
* [[Shapefile]]<br />
* [[KML]]<br />
* [[E00]] -- ArcInfo interchange file<br />
<br />
== Grid Formats -- see also raster formats, above ==<br />
<br />
== Point cloud ==<br />
* [[LAS]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/Flexible_Image_Transport_SystemFlexible Image Transport System2013-01-08T23:05:57Z<p>SwanQ: /* Identification */</p>
<hr />
<div>{|<br />
|[[File Formats]]<br />
| ><br />
|[[Electronic File Formats]]<br />
| ><br />
|[[Scientific Data formats]]<br />
| ><br />
|[[Flexible Image Transport System]]<br />
|}<br />
<br />
{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Scientific Data formats<br />
|extensions={{ext|fits}}<br />
|mimetypes={{mimetype|image/fits}}<br>{{mimetype|application/fits}}<br />
|pronom={{PRONOM|x-fmt/383}}<br />
}}<br />
<br />
== General description ==<br />
<br />
FITS (Flexible Image Transport System) is a heavily-used and well-standardised format for storing astronomical data. It can store both images and tables, and has basic but flexible support for metadata.<br />
<br />
The format is fundamentally rather simple; indeed it is simple enough that a basic reader can be constructed with a relatively small amount of effort, but this is rarely necessary, since there are readers and writers for a broad range of scientific programming languages.<br />
<br />
The metadata is stored as a list of key-value pairs, with the keys being up to eight characters long, and the values up to 70 characters. There are some standards, and several conventions, for the choices of keyword. These conventions generally interoperate well, but readers should be aware that collisions are possible.<br />
<br />
The format has been standardised in a sequence of papers in the journal Astronomy and Astrophysics, and a set of conventions for header metadata has been developed, over a number of years.<br />
<br />
== Other information ==<br />
<br />
The format is summarised in [http://en.wikipedia.org/wiki/FITS Wikipedia], which includes some history of the format.<br />
<br />
For further information, see:<br />
* Version 3 of FITS is described in <ref>William D Pence, L Chiappetti, Clive G Page, R A Shaw and E Stobie, ''Definition of the Flexible Image Transport System (FITS), version 3.0'', Astronomy and Astrophysics, '''524''', A42+ (2010) doi:10.1051/0004-6361/201015362, (ADS bibcode: [http://adsabs.harvard.edu/abs/1981A&AS...44..363W 1981A&AS...44..363W])</ref>, and this document has been approved by the [http://en.wikipedia.org/w/index.php?title=International_Astronomical_Union&oldid=520671540 IAU's] [http://fits.gsfc.nasa.gov/iaufwg/iaufwg.html FITS Working Group]. The document is also available [http://fits.gsfc.nasa.gov/standard30/fits_standard30.pdf online].<br />
* The <code>image/fits</code> and <code>application/fits</code> MIME types were registered in [http://www.ietf.org/rfc/rfc4047.txt RFC 4047].<br />
* Further information, including libraries and file samples, is available at the [http://fits.gsfc.nasa.gov FITS support office]<br />
<br />
== Software ==<br />
<br />
See the [http://fits.gsfc.nasa.gov FITS support office].<br />
<br />
== Sample files ==<br />
<br />
See the [http://fits.gsfc.nasa.gov FITS support office].<br />
<br />
== Identification ==<br />
<br />
Valid FITS files start with the sequence of characters <code>SIMPLE=T </code>.<br />
<br />
The common FITS file extensions are <code>.fits</code> and (less often) <code>.fts</code>.<br />
<br />
The <code>image/fits</code> and <code>application/fits</code> MIME types were registered in [http://www.ietf.org/rfc/rfc4047.txt RFC 4047].<br />
<br />
== References ==<br />
<br />
<references/></div>SwanQhttp://fileformats.archiveteam.org/wiki/Submission_Information_PackageSubmission Information Package2012-12-12T03:32:44Z<p>SwanQ: </p>
<hr />
<div>A Submission Information Package (SIP) is a set of digital objects accompanied by technical and institutional metadata, meant to be submitted to a [[Electronic Archival Depot]].<br />
<br />
==Related==<br />
{{related OAIS}}</div>SwanQhttp://fileformats.archiveteam.org/wiki/MJ2MJ22012-12-12T03:31:02Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|subcat2=JPEG2000<br />
|extensions={{ext|mj2}} {{ext|mjp2}}<br />
|mimetypes={{mimetype|video/mj2}}<br />
|pronom={{PRONOM|fmt/337}}<br />
}}<br />
'''MJ2''' (also known as Motion JPEG2000) is a video format defined by [http://www.jpeg.org/jpeg2000/j2kpart3.html Part 3] of the [http://www.jpeg.org/jpeg2000/ JPEG 2000 standard]. Note that the final standards are not freely available, but the [http://www.jpeg.org/jpeg2000/CDs15444.html committee drafts] are. [[MJ2]] supports audio as well.<br />
<br />
According to the specification MJ2 is one of several specifications with common formatting, including [[JPEG2000]], [[MPEG-4]], and [[Quicktime]], sharing a common definition for the structure of a file (a sequence of objects, called boxes for JPEG2000 and atoms for MP4 and QuickTime), and a common definition of the general structure of an object. Codestreams in Motion JPEG2000 files are JP2 codestreams, as defined for [[JPEG2000]].<br />
<br />
See also [[Wikipedia:JPEG 2000]].<br />
<br />
== Specifications ==<br />
<br />
* [http://www.jpeg.org/public/fcd15444-3.pdf Motion JPEG 2000] (committee draft).<br />
<br />
== Sample files ==<br />
<br />
* [http://www.openjpeg.org/samples/Speedway.mj2 Sample MJ2] created with [[OpenJPEG]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/VideoVideo2012-12-12T03:14:43Z<p>SwanQ: /* Unknown */ Motion JPEG2000 info is at MJ2</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|thiscat=Video<br />
}}<br />
<br />
==Pure video formats==<br />
These formats are "monolithic" video formats, meaning that the file format and the encoding of the video data are tied to each other.<br />
<br />
* [[Bink Video]] (BIK)<br />
* [[FLI]] and FLC (animation format used by older Autodesk products)<br />
* [[Enhanced VOB]]<br />
* [[GRASP GL]] animation format<br />
* [[RealVideo]]<br />
* [[Smacker]]/SMK (created by RadGameTools; mostly used in games)<br />
* [[WMV]]<br />
<br />
==Video container formats==<br />
These formats are only containers for video, which can contain videos in many different encodings (or even other data like audio)<br />
<br />
* [[ASF]]<br />
* [[AVI]]<br />
* [[FLV]]<br />
* [[MOV]]<br />
* [[MKV]]<br />
* [[MXF]]<br />
* [[Quicktime]]<br />
* [[Acorn Replay|Replay]]<br />
* [[VOB]]<br />
* [[VP8]]<br />
* [[WebM]]<br />
* [[OGG]] containers (with their variants OGM, OGV, etc.)<br />
<br />
==Video stream formats==<br />
These formats are raw bitstream formats commonly contained in one of the above containers (but not necessarily)<br />
<br />
* [[Apple Intermediate Codec]]<br />
* [[Cinepak]]<br />
* [[Dirac]]<br />
* [[H.264]]<br />
* [[HuffyYUV]]<br />
* [[Indeo]]<br />
* [[Moving Blocks]] - Acorn Replay stream<br />
* [[MPEG]] and all of its variants (MPEG2, MPEG4, etc.)<br />
** [[3ivx]] (this is just another fourcc for an MPEG4 variant)<br />
** [[DivX]] (this is essentially MPEG4 with some quirks)<br />
** [[XviD]] (another MPEG4 variant)<br />
* [[Sorenson]] Video Codec<br />
* [[Theora]]<br />
* [[VC-1]]<br />
* [[VC-3]]<br />
<br />
==Subtitle formats==<br />
* [[SUB]] and IDX ([[VobSub]] subtitle format)<br />
* [[SSA]] and ASS (SubStation Alpha)<br />
* [[SRT]] (SubRip)<br />
* [[SMI]] (SAMI subtitle format)<br />
* [[USF (subtitles)]] (Universal Subtitle Format)<br />
* [[SSF (subtitles)]] (Structured Subtitle Format)<br />
* [[CMML]] (Continuous Media Markup Language)<br />
* [[CVD]] (An SVCD subtitle format)<br />
* [[DVD]] (DVD subtitle format)<br />
* [[DXFP]] (Distribution Format Exchange Profile)<br />
* [[JACOsub]] (Subtitles for Amiga video)<br />
* [[Kate]] (Kate subtitle format)<br />
* [[OGT]] (Philips Overlay Graphics Text)<br />
* [[STL]] (Spruce Subtitle Format)<br />
* [[XSUB]] (XSUB subtitle format)<br />
<br />
==Television broadcast formats==<br />
* [[BTSC]] (NTSC with multichannel sound carrier)<br />
* [[NTSC]]<br />
* [[PAL]]<br />
* [[SECAM]]<br />
<br />
==Unknown==<br />
These formats still need to be sorted into the above categories<br />
* [[Ace Film]]<br />
* Animated [[GIF]]<br />
* [[AVS]]<br />
* [[Canopus ProCoder]]<br />
* [[Cineform]]<br />
* [[Cinema Craft Encoder]]<br />
* [[Elecard]]<br />
* [[InterVideo]]<br />
* [[MJ2]]<br />
* [[MainConcept]]<br />
* [[MSU Lossless Video Codec]]<br />
* [[NSD]] (Nero Super Video CD)<br />
* [[SheerVideo]]<br />
* [[TechSmith Screen Capture Codec]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/QuickTimeQuickTime2012-12-12T03:12:04Z<p>SwanQ: Relationship to MPEG-4</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|extensions={{ext|mov}}<br />
|mimetypes={{mimetype|video/quicktime}}<br />
|pronom={{PRONOM|x-fmt/384}}<br />
}}<br />
'''Quicktime''' is a container format developed by Apple Computer, Inc. It is usually used to wrap video content, but can also be used to wrap sound and still image data. <br />
<br />
The Quicktime format was used as the basis for the international standard [[MPEG-4]] format.<br />
<br />
== Specifications ==<br />
<br />
* [http://developer.apple.com/standards/classicquicktime.html Quicktime File Format Specification (classic, 2001)] <br />
* [http://developer.apple.com/mac/library/documentation/QuickTime/QTFF/ Quicktime File Format Specification (current, as of 2012)]<br />
<br />
== References ==<br />
<br />
*[http://en.wikipedia.org/wiki/QuickTime Quicktime : Wikipedia]</div>SwanQhttp://fileformats.archiveteam.org/wiki/QuickTimeQuickTime2012-12-12T03:09:05Z<p>SwanQ: /* References */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|extensions={{ext|mov}}<br />
|mimetypes={{mimetype|video/quicktime}}<br />
|pronom={{PRONOM|x-fmt/384}}<br />
}}<br />
'''Quicktime''' is a container format developed by Apple Computer, Inc. It is usually used to wrap video content, but can also be used to wrap sound and still image data.<br />
<br />
== Specifications ==<br />
<br />
* [http://developer.apple.com/standards/classicquicktime.html Quicktime File Format Specification (classic, 2001)] <br />
* [http://developer.apple.com/mac/library/documentation/QuickTime/QTFF/ Quicktime File Format Specification (current, as of 2012)]<br />
<br />
== References ==<br />
<br />
*[http://en.wikipedia.org/wiki/QuickTime Quicktime : Wikipedia]</div>SwanQhttp://fileformats.archiveteam.org/wiki/QuickTimeQuickTime2012-12-12T03:06:32Z<p>SwanQ: /* Specifications */</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|extensions={{ext|mov}}<br />
|mimetypes={{mimetype|video/quicktime}}<br />
|pronom={{PRONOM|x-fmt/384}}<br />
}}<br />
'''Quicktime''' is a container format developed by Apple Computer, Inc. It is usually used to wrap video content, but can also be used to wrap sound and still image data.<br />
<br />
== Specifications ==<br />
<br />
* [http://developer.apple.com/standards/classicquicktime.html Quicktime File Format Specification (classic, 2001)] <br />
* [http://developer.apple.com/mac/library/documentation/QuickTime/QTFF/ Quicktime File Format Specification (current, as of 2012)]<br />
<br />
== References ==<br />
<br />
*[http://en.wikipedia.org/wiki/QuickTime Wikipedia : Quicktime]</div>SwanQhttp://fileformats.archiveteam.org/wiki/QuickTimeQuickTime2012-12-12T03:04:31Z<p>SwanQ: Created page with "{{FormatInfo |formattype=electronic |subcat=Video |extensions={{ext|mov}} |mimetypes={{mimetype|video/quicktime}} |pronom={{PRONOM|x-fmt/384}} }} '''Quicktime''' is a containe..."</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|extensions={{ext|mov}}<br />
|mimetypes={{mimetype|video/quicktime}}<br />
|pronom={{PRONOM|x-fmt/384}}<br />
}}<br />
'''Quicktime''' is a container format developed by Apple Computer, Inc. It is usually used to wrap video content, but can also be used to wrap sound and still image data.<br />
<br />
== Specifications ==<br />
<br />
* [https://developer.apple.com/standards/classicquicktime.html Quicktime File Format Specification (classic, 2001)] <br />
* [https://developer.apple.com/mac/library/documentation/QuickTime/QTFF/ Quicktime File Format Specification (current, as of 2012)]<br />
<br />
== References ==<br />
<br />
*[http://en.wikipedia.org/wiki/QuickTime Wikipedia : Quicktime]</div>SwanQhttp://fileformats.archiveteam.org/wiki/MJ2MJ22012-12-12T02:46:07Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|subcat2=JPEG2000<br />
|extensions={{ext|mj2}} {{ext|mjp2}}<br />
|mimetypes={{mimetype|video/mj2}}<br />
|pronom={{PRONOM|fmt/337}}<br />
}}<br />
'''MJ2''' (also known as Motion JPEG2000) is a video format defined by [http://www.jpeg.org/jpeg2000/j2kpart3.html Part 3] of the [http://www.jpeg.org/jpeg2000/ JPEG 2000 standard]. Note that the final standards are not freely available, but the [http://www.jpeg.org/jpeg2000/CDs15444.html committee drafts] are. [[MJ2]] supports audio as well.<br />
<br />
According to the specification MJ2 is one of several specifications with common formatting, including [[JPEG2000]], [[MPEG4]], and [[Quicktime]], sharing a common definition for the structure of a file (a sequence of objects, called boxes for JPEG2000 and atoms for MP4 and QuickTime), and a common definition of the general structure of an object. Codestreams in Motion JPEG2000 files are JP2 codestreams, as defined for [[JPEG2000]].<br />
<br />
See also [[Wikipedia:JPEG 2000]].<br />
<br />
== Specifications ==<br />
<br />
* [http://www.jpeg.org/public/fcd15444-3.pdf Motion JPEG 2000] (committee draft).<br />
<br />
== Sample files ==<br />
<br />
* [http://www.openjpeg.org/samples/Speedway.mj2 Sample MJ2] created with [[OpenJPEG]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/MJ2MJ22012-12-12T02:22:19Z<p>SwanQ: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|subcat2=JPEG2000<br />
|extensions={{ext|mj2}} {{ext|mjp2}}<br />
|mimetypes={{mimetype|video/mj2}}<br />
|pronom={{PRONOM|fmt/337}}<br />
}}<br />
'''MJ2''' (also known as Motion JPEG 2000) is a video format defined by [http://www.jpeg.org/jpeg2000/j2kpart3.html Part 3] of the [http://www.jpeg.org/jpeg2000/ JPEG 2000 standard]. Note that the final standards are not freely available, but the [http://www.jpeg.org/jpeg2000/CDs15444.html committee drafts] are. [[MJ2]] supports audio as well.<br />
<br />
According to the specification MJ2 is one of several specifications with common formatting, including [[JPEG2000]], [[MPEG-4]], and [[Quicktime]], sharing a common definition for the structure of a file (a sequence of objects, called boxes here and atoms in MP4 and QuickTime), and a common definition of the general structure of an object.<br />
<br />
<br />
See also [[Wikipedia:JPEG 2000]].<br />
<br />
== Specifications ==<br />
<br />
* [http://www.jpeg.org/public/fcd15444-3.pdf Motion JPEG 2000] (committee draft).<br />
<br />
== Sample files ==<br />
<br />
* [http://www.openjpeg.org/samples/Speedway.mj2 Sample MJ2] created with [[OpenJPEG]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/MJ2MJ22012-12-12T02:21:39Z<p>SwanQ: Added relationship to other formats</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
|subcat2=JPEG2000<br />
|extensions={{ext|mj2}} {{ext|mjp2}}<br />
|mimetypes={{mimetype|video/mj2}}<br />
|pronom={{PRONOM|fmt/337}}<br />
}}<br />
'''MJ2''' (also known as Motion JPEG 2000) is a video format defined by [http://www.jpeg.org/jpeg2000/j2kpart3.html Part 3] of the [http://www.jpeg.org/jpeg2000/ JPEG 2000 standard]. Note that the final standards are not freely available, but the [http://www.jpeg.org/jpeg2000/CDs15444.html committee drafts] are. [[MJ2]] supports audio as well.<br />
<br />
According to the specification MJ2 is one of several specifications with common formatting, including [[JPEG 2000]], [[MPEG-4]], and [[Quiktime]], sharing a common definition for the structure of a file (a sequence of objects, called boxes here and atoms in MP4 and QuickTime), and a common definition of the general structure of an object.<br />
<br />
<br />
See also [[Wikipedia:JPEG 2000]].<br />
<br />
== Specifications ==<br />
<br />
* [http://www.jpeg.org/public/fcd15444-3.pdf Motion JPEG 2000] (committee draft).<br />
<br />
== Sample files ==<br />
<br />
* [http://www.openjpeg.org/samples/Speedway.mj2 Sample MJ2] created with [[OpenJPEG]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/IndeoIndeo2012-12-04T03:07:58Z<p>SwanQ: Wikipedia link</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
Several versions of '''Indeo''' codec were developed by Intel Corporation, starting in 1992, and the latest versions (video versions 4 & 5, and audio version 2.5) are now made available by Ligos Corporation, which acquired the technology in 2000. Indeo was one of the first codecs allowing full-speed video playback without using hardware acceleration. Indeo Video Codec, Version 3 used vector quantization. Indeo Video Codec, Versions 4 & 5 use wavelet compression.<br />
<br />
The Ligos website states that Indeo, meaning the Ligos Indeo Codecs package, is not supported for use with Microsoft's Vista or Windows 7 operating systems, or any Apple Mac operating systems. <br />
<br />
The Ligos [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] page reports inconsistent bundling of an Indeo Version 5 codec by Microsoft in versions of Windows XP, Vista, and 7.<br />
<br />
== Software ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] page from Ligos Corporation provides a link to download the Ligos Indeo Codecs for Windows and states:<br />
: "As an option to meet the needs of those Windows (95, 98, ME, XP and NT/2000 only) users who require Indeo codecs, Ligos has created an enhanced bundle of the Indeo codecs called Ligos Indeo Codecs. The Indeo Codecs include Indeo Video version 5.2, as well as support for the older Indeo Video 4.5 and Indeo Audio 2.5 codecs (the 3.x video codec is no longer available nor supported). The Ligos Indeo Codecs package is available for purchase and download through our electronic store for $14.95. There is no free or demo version available."<br />
<br />
== References ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] page from Ligos Corporation<br />
* [http://ligos.com/pdf_docs/Indeo_doc.pdf Ligos Corporation Indeo® Video and Audio Codecs Technical Documentation] Describes the codecs rather than the bitstream format.<br />
* [http://ligos.com/pdf_docs/Indeo_FAQ.pdf Ligos Corporation Indeo® Frequently Asked Questions]<br />
* [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] from Ligos Corporation.<br />
* [http://en.wikipedia.org/wiki/Indeo Wikipedia : Indeo]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000065.shtml Indeo Video Codec, Version 3, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000085.shtml Indeo Video Codec, Version 5, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/IndeoIndeo2012-12-04T03:00:31Z<p>SwanQ: added date of development, etc.</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
Several versions of '''Indeo''' codec were developed by Intel Corporation, starting in 1992, and the latest versions (video versions 4 & 5, and audio version 2.5) are now made available by Ligos Corporation, which acquired the technology in 2000. Indeo was one of the first codecs allowing full-speed video playback without using hardware acceleration. Indeo Video Codec, Version 3 used vector quantization. Indeo Video Codec, Versions 4 & 5 use wavelet compression.<br />
<br />
The Ligos website states that Indeo, meaning the Ligos Indeo Codecs package, is not supported for use with Microsoft's Vista or Windows 7 operating systems, or any Apple Mac operating systems. <br />
<br />
The Ligos [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] page reports inconsistent bundling of an Indeo Version 5 codec by Microsoft in versions of Windows XP, Vista, and 7.<br />
<br />
== Software ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation provides a link to download the Ligos Indeo Codecs for Windows and states:<br />
: "As an option to meet the needs of those Windows (95, 98, ME, XP and NT/2000 only) users who require Indeo codecs, Ligos has created an enhanced bundle of the Indeo codecs called Ligos Indeo Codecs. The Indeo Codecs include Indeo Video version 5.2, as well as support for the older Indeo Video 4.5 and Indeo Audio 2.5 codecs (the 3.x video codec is no longer available nor supported). The Ligos Indeo Codecs package is available for purchase and download through our electronic store for $14.95. There is no free or demo version available."<br />
<br />
== References ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation<br />
* [http://ligos.com/pdf_docs/Indeo_doc.pdf Ligos Corporation Indeo® Video and Audio Codecs Technical Documentation] Describes the codecs rather than the bitstream format.<br />
* [http://ligos.com/pdf_docs/Indeo_FAQ.pdf Ligos Corporation Indeo® Frequently Asked Questions]<br />
* [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] from Ligos Corporation.<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000065.shtml Indeo Video Codec, Version 3, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000085.shtml Indeo Video Codec, Version 5, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/IndeoIndeo2012-12-04T02:56:11Z<p>SwanQ: Microsoft bundling</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
Several versions of '''Indeo''' codec were developed by Intel Corporation and the latest versions (video versions 4 & 5, and audio version 2.5) are now made available by Ligos Corporation, which acquired the technology in 2000. Indeo Video Codec, Version 3 used vector quantization. Indeo Video Codec, Versions 4 & 5 use wavelet compression.<br />
<br />
The Ligos website states that Indeo, meaning the Ligos Indeo Codecs package, is not supported for use with Microsoft's Vista or Windows 7 operating systems, or any Apple Mac operating systems. <br />
<br />
The Ligos [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] page reports inconsistent bundling of an Indeo Version 5 codec by Microsoft in versions of Windows XP, Vista, and 7.<br />
<br />
== Software ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation provides a link to download the Ligos Indeo Codecs for Windows and states:<br />
: "As an option to meet the needs of those Windows (95, 98, ME, XP and NT/2000 only) users who require Indeo codecs, Ligos has created an enhanced bundle of the Indeo codecs called Ligos Indeo Codecs. The Indeo Codecs include Indeo Video version 5.2, as well as support for the older Indeo Video 4.5 and Indeo Audio 2.5 codecs (the 3.x video codec is no longer available nor supported). The Ligos Indeo Codecs package is available for purchase and download through our electronic store for $14.95. There is no free or demo version available."<br />
<br />
== References ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation<br />
* [http://ligos.com/pdf_docs/Indeo_doc.pdf Ligos Corporation Indeo® Video and Audio Codecs Technical Documentation] Describes the codecs rather than the bitstream format.<br />
* [http://ligos.com/pdf_docs/Indeo_FAQ.pdf Ligos Corporation Indeo® Frequently Asked Questions]<br />
* [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] from Ligos Corporation.<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000065.shtml Indeo Video Codec, Version 3, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000085.shtml Indeo Video Codec, Version 5, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/IndeoIndeo2012-12-04T02:47:53Z<p>SwanQ: Created page with "{{FormatInfo |formattype=electronic |subcat=Video }} Several versions of '''Indeo''' codec were developed by Intel Corporation and the latest versions (video versions 4 & 5, ..."</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
Several versions of '''Indeo''' codec were developed by Intel Corporation and the latest versions (video versions 4 & 5, and audio version 2.5) are now made available by Ligos Corporation, which acquired the technology in 2000. Indeo Video Codec, Version 3 used vector quantization. Indeo Video Codec, Versions 4 & 5 use wavelet compression.<br />
<br />
The Ligos website states that Indeo, meaning the Ligos Indeo Codecs package, is not supported for use with Microsoft's Vista or Windows 7 operating systems, or any Apple Mac operating systems. <br />
<br />
== Software ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation provides a link to download the Ligos Indeo Codecs for Windows and states:<br />
: "As an option to meet the needs of those Windows (95, 98, ME, XP and NT/2000 only) users who require Indeo codecs, Ligos has created an enhanced bundle of the Indeo codecs called Ligos Indeo Codecs. The Indeo Codecs include Indeo Video version 5.2, as well as support for the older Indeo Video 4.5 and Indeo Audio 2.5 codecs (the 3.x video codec is no longer available nor supported). The Ligos Indeo Codecs package is available for purchase and download through our electronic store for $14.95. There is no free or demo version available."<br />
<br />
== References ==<br />
* [http://ligos.com/index.php/home/products/indeo/ Indeo] from Ligos Corporation<br />
* [http://ligos.com/pdf_docs/Indeo_doc.pdf Ligos Corporation Indeo® Video and Audio Codecs Technical Documentation] Describes the codecs rather than the bitstream format.<br />
* [http://ligos.com/pdf_docs/Indeo_FAQ.pdf Ligos Corporation Indeo® Frequently Asked Questions]<br />
* [http://ligos.com/index.php/home/support/indeosupport/ Indeo Support] from Ligos Corporation.<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000065.shtml Indeo Video Codec, Version 3, from Library of Congress resource on Sustainability of Digital Formats]<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000085.shtml Indeo Video Codec, Version 5, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/SorensonSorenson2012-11-30T04:40:22Z<p>SwanQ: added link to H.264</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
A '''Sorenson''' video codec has been built into Quicktime products since Quicktime 3.0. However, Sorenson has developed more than one proprietary codec, certainly Version 1 and Version 3. A [http://forum.sorensonmedia.com/forum/showthread.php?3649-best-H264-codec September 2012 statement] in a product forum hosted by Sorenson Media also mentions "Sorenson [[H.264]]" and "Sorenson MPEG4 pro" which presumably relate to bitstreams in open standard forms generated by Sorenson software.<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/Sorenson_codec Wikipedia : Sorenson codec]<br />
* [http://wiki.multimedia.cx/index.php?title=Sorenson_Video_1 Multimediawiki : Sorenson Video 1]<br />
* [http://wiki.multimedia.cx/index.php?title=Sorenson_Video_3 Multimediawiki : Sorenson Video 3]<br />
* [http://www.siggraph.org/education/materials/HyperGraph/video/codecs/SorensonBrochure.pdf Sorenson Video QuickTime codec] 1998 brochure from developer.<br />
* [http://www.siggraph.org/education/materials/HyperGraph/video/codecs/Sorenson.html Codec Central : Sorenson Video] Content appears to date from 1998.<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000066.shtml Sorenson Video Codec, version 3, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQhttp://fileformats.archiveteam.org/wiki/VideoVideo2012-11-30T04:38:57Z<p>SwanQ: /* Video stream formats */</p>
<hr />
<div>{|<br />
|[[File Formats]]<br />
| ><br />
|[[Electronic File Formats]]<br />
| ><br />
|[[Video]]<br />
|}<br />
<br />
==Pure video formats==<br />
These formats are "monolithic" video formats, meaning that the file format and the encoding of the video data are tied to each other.<br />
<br />
* [[Bink Video]] (BIK)<br />
* [[FLI]] and FLC (animation format used by older Autodesk products)<br />
* [[Enhanced VOB]]<br />
* [[GRASP GL]] animation format<br />
* [[RealVideo]]<br />
* [[Smacker]]/SMK (created by RadGameTools; mostly used in games)<br />
* [[WMV]]<br />
<br />
==Video container formats==<br />
These formats are only containers for video, which can contain videos in many different encodings (or even other data like audio)<br />
<br />
* [[ASF]]<br />
* [[AVI]]<br />
* [[FLV]]<br />
* [[MOV]]<br />
* [[MKV]]<br />
* [[MXF]]<br />
* [[Quicktime]]<br />
* [[Acorn Replay|Replay]]<br />
* [[VOB]]<br />
* [[VP8]]<br />
* [[WebM]]<br />
* [[OGG]] containers (with their variants OGM, OGV, etc.)<br />
<br />
==Video stream formats==<br />
These formats are raw bitstream formats commonly contained in one of the above containers (but not necessarily)<br />
<br />
* [[Apple Intermediate Codec]]<br />
* [[Cinepak]]<br />
* [[Dirac]]<br />
* [[H.264]]<br />
* [[HuffyYUV]]<br />
* [[Indeo]]<br />
* [[Moving Blocks]] - Acorn Replay stream<br />
* [[MPEG]] and all of its variants (MPEG2, MPEG4, etc.)<br />
** [[3ivx]] (this is just another fourcc for an MPEG4 variant)<br />
** [[DivX]] (this is essentially MPEG4 with some quirks)<br />
** [[XviD]] (another MPEG4 variant)<br />
* [[Sorenson]] Video Codec<br />
* [[Theora]]<br />
* [[VC-1]]<br />
* [[VC-3]]<br />
<br />
==Subtitle formats==<br />
* [[SUB]] and IDX ([[VobSub]] subtitle format)<br />
* [[SSA]] and ASS (SubStation Alpha)<br />
* [[SRT]] (SubRip)<br />
* [[SMI]] (SAMI subtitle format)<br />
* [[USF (subtitles)]] (Universal Subtitle Format)<br />
* [[SSF (subtitles)]] (Structured Subtitle Format)<br />
* [[CMML]] (Continuous Media Markup Language)<br />
* [[CVD]] (An SVCD subtitle format)<br />
* [[DVD]] (DVD subtitle format)<br />
* [[DXFP]] (Distribution Format Exchange Profile)<br />
* [[JACOsub]] (Subtitles for Amiga video)<br />
* [[Kate]] (Kate subtitle format)<br />
* [[OGT]] (Philips Overlay Graphics Text)<br />
* [[STL]] (Spruce Subtitle Format)<br />
* [[XSUB]] (XSUB subtitle format)<br />
<br />
==Television broadcast formats==<br />
* [[BTSC]] (NTSC with multichannel sound carrier)<br />
* [[NTSC]]<br />
* [[PAL]]<br />
* [[SECAM]]<br />
<br />
==Unknown==<br />
These formats still need to be sorted into the above categories<br />
* [[Ace Film]]<br />
* Animated [[GIF]]<br />
* [[AVS]]<br />
* [[Canopus ProCoder]]<br />
* [[Cineform]]<br />
* [[Cinema Craft Encoder]]<br />
* [[Elecard]]<br />
* [[InterVideo]]<br />
* [[JPEG2000]]<br />
* [[MainConcept]]<br />
* [[MSU Lossless Video Codec]]<br />
* [[NSD]] (Nero Super Video CD)<br />
* [[SheerVideo]]<br />
* [[TechSmith Screen Capture Codec]]<br />
<br />
[[Category:Video| ]]</div>SwanQhttp://fileformats.archiveteam.org/wiki/SorensonSorenson2012-11-30T04:36:52Z<p>SwanQ: distinguish proprietary formats from open standard video stream formats</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Video<br />
}}<br />
<br />
A '''Sorenson''' video codec has been built into Quicktime products since Quicktime 3.0. However, Sorenson has developed more than one proprietary codec, certainly Version 1 and Version 3. A [http://forum.sorensonmedia.com/forum/showthread.php?3649-best-H264-codec September 2012 statement] in a product forum hosted by Sorenson Media also mentions "Sorenson H.264" and "Sorenson MPEG4 pro" which presumably relate to bitstreams in open standard forms generated by Sorenson software.<br />
<br />
== References ==<br />
* [http://en.wikipedia.org/wiki/Sorenson_codec Wikipedia : Sorenson codec]<br />
* [http://wiki.multimedia.cx/index.php?title=Sorenson_Video_1 Multimediawiki : Sorenson Video 1]<br />
* [http://wiki.multimedia.cx/index.php?title=Sorenson_Video_3 Multimediawiki : Sorenson Video 3]<br />
* [http://www.siggraph.org/education/materials/HyperGraph/video/codecs/SorensonBrochure.pdf Sorenson Video QuickTime codec] 1998 brochure from developer.<br />
* [http://www.siggraph.org/education/materials/HyperGraph/video/codecs/Sorenson.html Codec Central : Sorenson Video] Content appears to date from 1998.<br />
* [http://www.digitalpreservation.gov/formats/fdd/fdd000066.shtml Sorenson Video Codec, version 3, from Library of Congress resource on Sustainability of Digital Formats]</div>SwanQ