Just Solve the File Format Problem - User contributions [en]

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/WebStart.php on line 97

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/WebStart.php on line 134

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/LocalSettings.php on line 137

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/LocalSettings.php on line 139

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/LocalSettings.php on line 144

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/LocalSettings.php on line 145

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/LocalSettings.php on line 153

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/WebStart.php on line 150

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/Setup.php on line 382

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/Setup.php on line 383

Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/Setup.php on line 384

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:97) in /usr/local/www/mediawiki/includes/Feed.php on line 229

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:97) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:97) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:97) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38
http://fileformats.archiveteam.org/api.php?action=feedcontributions&feedformat=atom&user=Ross-spencer Just Solve the File Format Problem - User contributions [en] 2025-05-22T07:54:03Z User contributions MediaWiki 1.19.2 http://fileformats.archiveteam.org/wiki/Category:File_formats_with_extension_.ttl Category:File formats with extension .ttl 2025-05-14T08:12:51Z

Ross-spencer: Add ttl category <hr /> <div>[[Category:File formats by extension|T]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Turtle Turtle 2025-05-14T08:11:45Z

Ross-spencer: Add entry for Turtle <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Metadata |extension={{ext|ttl}} }} '''Turtle''' (Terse RDF Triple Language) is a W3C Recommendation described a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. == Examples == Examples from the recommendation. Describes the relationship between Green Goblin and Spiderman: <pre> @base <http://example.org/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix rel: <http://www.perceive.net/schemas/relationship/> . <#green-goblin> rel:enemyOf <#spiderman> ; a foaf:Person ; # in the context of the Marvel universe foaf:name "Green Goblin" . <#spiderman> rel:enemyOf <#green-goblin> ; a foaf:Person ; foaf:name "Spiderman", "Ð§ÐµÐ»Ð¾Ð²ÐµÐº-Ð¿Ð°ÑƒÐº"@ru . </pre> An example showing how numbers can be encoded: <pre> @prefix : <http://example.org/elements> . <http://en.wikipedia.org/wiki/Helium> :atomicNumber 2 ; # xsd:integer :atomicMass 4.002602 ; # xsd:decimal :specificGravity 1.663E-4 . # xsd:double </pre> An example of Turtle embedded in a HTML document: <pre> <script type="text/turtle"> @prefix dc: <http://purl.org/dc/terms/> . @prefix frbr: <http://purl.org/vocab/frbr/core#> . <http://books.example.com/works/45U8QJGZSQKDH8N> a frbr:Work ; dc:creator "Wil Wheaton"@en ; dc:title "Just a Geek"@en ; frbr:realization <http://books.example.com/products/9780596007683.BOOK>, <http://books.example.com/products/9780596802189.EBOOK> . <http://books.example.com/products/9780596007683.BOOK> a frbr:Expression ; dc:type <http://books.example.com/product-types/BOOK> . <http://books.example.com/products/9780596802189.EBOOK> a frbr:Expression ; dc:type <http://books.example.com/product-types/EBOOK> . </script> </pre> == Links == * [https://www.w3.org/TR/turtle/ W3C recommendation for RDF 1.1 Turtle] * [https://en.wikipedia.org/wiki/Turtle_(syntax) Turtle Syntax (Wikipedia)] [[Category:W3C]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/DCAT DCAT 2025-05-14T08:03:33Z

Ross-spencer: FIx internal link <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Metadata }} '''DCAT''' (Data Catalogue vocabulary) is a W3C Recommendation described as being an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. The [https://www.w3.org/TR/vocab-dcat-3/ recommendation] defines the schema and provides examples for its use. == Identification == RDF-based documents containing key elements of the vocabulary might be probabilistically identified as DCAT, or at least, as a dataset using DCAT vocabulary elements. A <code>Dataset</code> (collection of data, published or curated by a single agent or identifiable community) example from the recommendation ([[Turtle]]): <pre> ex:dataset-001 a dcat:Dataset ; dcterms:title "Imaginary dataset"@en ; dcterms:title "Conjunto de datos imaginario"@es ; dcat:keyword "accountability"@en, "transparency"@en, "payments"@en ; dcat:keyword "responsabilidad"@es, "transparencia"@es, "pagos"@es ; dcterms:creator ex:finance-employee-001 ; dcterms:issued "2011-12-05"^^xsd:date ; dcterms:modified "2011-12-15"^^xsd:date ; dcat:contactPoint <http://dcat.example.org/transparency-office/contact> ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate "2011-07-01"^^xsd:date ; dcat:endDate "2011-09-30"^^xsd:date ; ]; dcat:temporalResolution "P1D"^^xsd:duration ; dcterms:spatial <http://sws.geonames.org/6695072/> ; dcat:spatialResolutionInMeters "30.0"^^xsd:decimal ; dcterms:publisher ex:finance-ministry ; dcterms:language <http://id.loc.gov/vocabulary/iso639-1/en> ; dcterms:accrualPeriodicity <http://purl.org/linked-data/sdmx/2009/code#freq-W> ; dcat:distribution ex:dataset-001-csv ; . </pre> A <code>Distriubtion</code> (an accessible form of a dataset such as a downloadable file) example from the recommendation (in [[Turtle]]): <pre> ex:dataset-001-csv a dcat:Distribution ; dcat:downloadURL <http://dcat.example.org/files/001.csv> ; dcterms:title "CSV distribution of imaginary dataset 001"@en ; dcterms:title "distribuciÃ³n en CSV del conjunto de datos imaginario 001"@es ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:byteSize "5120"^^xsd:nonNegativeInteger ; . </pre> == Implementations == * European DCAT Application Profile: [[DCAT-AP]] == Links == * [https://www.w3.org/TR/vocab-dcat-3/ Data Catalog Vocabulary (DCAT) - Version 3] [[Category:Metadata]] [[Category:W3C]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/DCAT DCAT 2025-05-14T08:02:39Z

Ross-spencer: Add DCAT <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Metadata }} '''DCAT''' (Data Catalogue vocabulary) is a W3C Recommendation described as being an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. The [https://www.w3.org/TR/vocab-dcat-3/ recommendation] defines the schema and provides examples for its use. == Identification == RDF-based documents containing key elements of the vocabulary might be probabilistically identified as DCAT, or at least, as a dataset using DCAT vocabulary elements. A <code>Dataset</code> (collection of data, published or curated by a single agent or identifiable community) example from the recommendation ([Turtle]): <pre> ex:dataset-001 a dcat:Dataset ; dcterms:title "Imaginary dataset"@en ; dcterms:title "Conjunto de datos imaginario"@es ; dcat:keyword "accountability"@en, "transparency"@en, "payments"@en ; dcat:keyword "responsabilidad"@es, "transparencia"@es, "pagos"@es ; dcterms:creator ex:finance-employee-001 ; dcterms:issued "2011-12-05"^^xsd:date ; dcterms:modified "2011-12-15"^^xsd:date ; dcat:contactPoint <http://dcat.example.org/transparency-office/contact> ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate "2011-07-01"^^xsd:date ; dcat:endDate "2011-09-30"^^xsd:date ; ]; dcat:temporalResolution "P1D"^^xsd:duration ; dcterms:spatial <http://sws.geonames.org/6695072/> ; dcat:spatialResolutionInMeters "30.0"^^xsd:decimal ; dcterms:publisher ex:finance-ministry ; dcterms:language <http://id.loc.gov/vocabulary/iso639-1/en> ; dcterms:accrualPeriodicity <http://purl.org/linked-data/sdmx/2009/code#freq-W> ; dcat:distribution ex:dataset-001-csv ; . </pre> A <code>Distriubtion</code> (an accessible form of a dataset such as a downloadable file) example from the recommendation (in [Turtle]): <pre> ex:dataset-001-csv a dcat:Distribution ; dcat:downloadURL <http://dcat.example.org/files/001.csv> ; dcterms:title "CSV distribution of imaginary dataset 001"@en ; dcterms:title "distribuciÃ³n en CSV del conjunto de datos imaginario 001"@es ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:byteSize "5120"^^xsd:nonNegativeInteger ; . </pre> == Implementations == * European DCAT Application Profile: [[DCAT-AP]] == Links == * [https://www.w3.org/TR/vocab-dcat-3/ Data Catalog Vocabulary (DCAT) - Version 3] [[Category:Metadata]] [[Category:W3C]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Lottie Lottie 2025-05-02T10:33:30Z

Ross-spencer: Add software and more sample info <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Animation |extensions={{ext|json}} }} [[Lottie]] is a modern animated file format. == Software == * [https://lottiefiles.com/ lottiefiles.com] * [https://app.lottiefiles.com/ app.lottiefiles.com] * [https://github.com/Samsung/rlottie rlottie] * [http://snisurset.net/code/abydos/ abydos] == Sample files == Sample files can be downloaded from [https://lottiefiles.com/ lottiefiles.com] and created and downloaded in [https://app.lottiefiles.com/ app.lottiefiles.com]. Samples are also available at dexvert: {{DexvertSamples|image/lottie}}</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Tabular_Data_Package Tabular Data Package 2025-04-18T17:04:33Z

Ross-spencer: Add information about Data Package <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Databases }} == General description == This page describes '''Tabular Data Package''', formerly known as '''Simple Data Format''' (but not related to [[Simple Data format]] by George H. Fisher). It is described as a "simple data publishing format for publishing and sharing data". It is created by the Data Protocols Team (in 2011?), whose manifesto is at http://dataprotocols.org/manifesto/. This does not however identify the Data Protocols Team or its affiliations. The draft specification is at http://dataprotocols.org/tabular-data-package/. The format's focus is simplicity and web usage. It is based on [[CSV]] for the base data and [[JSON]] for schema, metadata and lined data aspects. The original source of the specification, dataprotocols.org is now now Data Package at [https://datapackage.org/ datapackage.org] from Frictionless Data. Their specifications are also available on their [https://github.com/frictionlessdata/datapackage GitHub]. == Other information == There is no known Wikipedia page for the Data Protocols Team or this version of the Tabular Data Package. == Source code == * [https://github.com/frictionlessdata/datapackage datapackage on GitHub] == References == * [https://datapackage.org/ datapackage.org] * [https://github.com/frictionlessdata/datapackage Data Package GitHub repo]. [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/JSON_Table_Schema JSON Table Schema 2025-04-18T17:03:07Z

Ross-spencer: Add information about Data Package <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''JSON Table Schema''' is a method, expressable in [[JSON]], of specifying the field structure of tabular data, for instance a spreadsheet or [[CSV]] file. It is "in competition" with [[CSV Schema]] as a way to describe a CSV data structure. It can be accompanied by a [[CSV Dialect Description Format]] file to describe the specifics of the delimiter and quoting rules in a CSV or other delimited file. The original source of the specification, dataprotocols.org is now now Data Package at [https://datapackage.org/ datapackage.org] from Frictionless Data. Their specifications are also available on their [https://github.com/frictionlessdata/datapackage GitHub]. == Links == * [https://github.com/frictionlessdata/datapackage Data Package GitHub repo]. * [http://dataprotocols.org/json-table-schema/ Official description/spec] * [https://web.archive.org/web/20230519194832/http://dataprotocols.org/json-table-schema/ official documentation on archive.org] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/CSV_Dialect_Description_Format CSV Dialect Description Format 2025-04-18T17:02:26Z

Ross-spencer: Add info about Data Package <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''CSV Dialect Dscription Format''' is a [[JSON]]-based format for describing the particular rules for a variety of delimited files, such as [[CSV]] or [[tab delimited]]. It does not describe the format of the data fields within a record of the file; this may be done with [[JSON Table Schema]] or [[CSV Schema]]. The original source of the specification, dataprotocols.org is now now Data Package at [https://datapackage.org/ datapackage.org] from Frictionless Data. Their specifications are also available on their [https://github.com/frictionlessdata/datapackage GitHub]. == Examples == === 1.0 === <pre> { "csvddf_version": 1.0, "dialect": { "delimiter": ",", "doublequote": false, "lineterminator": "\r\n", "quotechar": "\"", "skipinitialspace": false } } </pre> === 1.2 === <pre> { "csvddfVersion": 1.2, "delimiter": ",", "doubleQuote": true, "lineTerminator": "\r\n", "quoteChar": "\"", "skipInitialSpace": true, "header": true } </pre> == Links == * [https://github.com/frictionlessdata/datapackage Data Package GitHub repo]. * [http://dataprotocols.org/csv-dialect/ Official description/spec] * [https://web.archive.org/web/20131017022844/http://dataprotocols.org/csv-dialect/ Official description/spec via archive.org (v1.0)] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Tabular_Data_Package Tabular Data Package 2025-04-18T14:50:44Z

Ross-spencer: Add github repo <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Databases }} == General description == This page describes '''Tabular Data Package''', formerly known as '''Simple Data Format''' (but not related to [[Simple Data format]] by George H. Fisher). It is described as a "simple data publishing format for publishing and sharing data". It is created by the Data Protocols Team (in 2011?), whose manifesto is at http://dataprotocols.org/manifesto/. This does not however identify the Data Protocols Team or its affiliations. The draft specification is at http://dataprotocols.org/tabular-data-package/. The format's focus is simplicity and web usage. It is based on [[CSV]] for the base data and [[JSON]] for schema, metadata and lined data aspects. == Other information == There is no known Wikipedia page for the Data Protocols Team or this version of the Tabular Data Package. == Source code == * [https://github.com/frictionlessdata/datapackage datapackage on GitHub] == References == Apart from the manifesto and specification, nothing is known. [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Sketch Sketch 2025-04-18T14:38:13Z

Ross-spencer: Update links <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Graphics |extensions={{ext|sketch}} |released=2010 }} '''Sketch''' (sometimes called '''Sketch App''') is a proprietary vector graphics editor for Mac OS X, developed by a company named ''Bohemian''. It has a native '''.sketch''' file format. == Disambiguation == There are a lot of other things named Sketch, such as [[Skencil SK]], [[EPOC Sketch]], and [[AutoSketch]]. == Format details == Apparently, Sketch formats through v42 are based on [[SQLite]]. Later versions are based on [[JSON]]. == Format documentation == * [https://developer.sketch.com/file-format/ sketch file format]. == Reference files == * [https://github.com/sketch-hq/sketch-document/blob/4493900abbfa49ae82fbcb8ad85cccf2cc2256b0/.yarn/cache/%40sketch-hq-sketch-reference-files-2.3.0.tgz Sketch reference files (.tgz)] * [https://github.com/sketch-hq/sketch-document/tree/4493900abbfa49ae82fbcb8ad85cccf2cc2256b0/packages/file/src/__tests__ Sketch test files] == Links == * [[Wikipedia: Sketch (application)]] * [https://www.sketchapp.com/ Main website] * http://sketchapp.rocks/ * [https://www.sitepoint.com/need-know-sketchs-new-file-format/ Why You Need to Know About Sketchâ€™s New File Format] * [https://github.com/sketch-hq/sketch-document Sketch monorepo with format .sketch examples] [[Category:SQLite based file formats]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Sketch Sketch 2025-04-18T14:36:58Z

Ross-spencer: <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Graphics |extensions={{ext|sketch}} |released=2010 }} '''Sketch''' (sometimes called '''Sketch App''') is a proprietary vector graphics editor for Mac OS X, developed by a company named ''Bohemian''. It has a native '''.sketch''' file format. == Disambiguation == There are a lot of other things named Sketch, such as [[Skencil SK]], [[EPOC Sketch]], and [[AutoSketch]]. == Format details == Apparently, Sketch formats through v42 are based on [[SQLite]]. Later versions are based on [[JSON]]. == Format documentation == * [https://developer.sketch.com/file-format/ sketch file format]. == Reference files == * [https://github.com/sketch-hq/sketch-document/blob/4493900abbfa49ae82fbcb8ad85cccf2cc2256b0/.yarn/cache/%40sketch-hq-sketch-reference-files-2.3.0.tgz Sketch reference files (.tgz)] == Links == * [[Wikipedia: Sketch (application)]] * [https://www.sketchapp.com/ Main website] * http://sketchapp.rocks/ * [https://www.sitepoint.com/need-know-sketchs-new-file-format/ Why You Need to Know About Sketchâ€™s New File Format] * [https://github.com/sketch-hq/sketch-document sketch monorepo with format .sketch examples] [[Category:SQLite based file formats]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Sketch Sketch 2025-04-18T14:34:41Z

Ross-spencer: Add examples and links to docs <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Graphics |extensions={{ext|sketch}} |released=2010 }} '''Sketch''' (sometimes called '''Sketch App''') is a proprietary vector graphics editor for Mac OS X, developed by a company named ''Bohemian''. It has a native '''.sketch''' file format. == Disambiguation == There are a lot of other things named Sketch, such as [[Skencil SK]], [[EPOC Sketch]], and [[AutoSketch]]. == Format details == Apparently, Sketch formats through v42 are based on [[SQLite]]. Later versions are based on [[JSON]]. == Format documentation == * [https://developer.sketch.com/file-format/ sketch file format]. == Links == * [[Wikipedia: Sketch (application)]] * [https://www.sketchapp.com/ Main website] * http://sketchapp.rocks/ * [https://www.sitepoint.com/need-know-sketchs-new-file-format/ Why You Need to Know About Sketchâ€™s New File Format] * [https://github.com/sketch-hq/sketch-document sketch monorepo with format .sketch examples] [[Category:SQLite based file formats]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Scratch_2.0_File_Format Scratch 2.0 File Format 2025-04-18T14:22:01Z

Ross-spencer: Add examples for 2.0 <hr /> <div>{{FormatInfo |subcat=Source code |extensions={{ext|sb2}}, {{ext|sprite2}} }} The '''Scratch 2.0 File Format''' saves projects in version 2.0 of the [[Scratch]] programming language. Scratch is a language designed to teach programming to young children. Since the program code consists of graphical tiles rather than text-based source code, a binary format was used for the earlier [[Scratch 1.4 File Format]], but the format has changed with 2.0. Scratch 2.0 runs from a web browser, so no installation is needed as with the earlier versions. Registered users can save their programs on the server, but unregistered users can still run Scratch online and upload/download programs saved on their own computer. Scratch projects are stored in files with a '''.sb2''' extension. The contents are [[ZIP]]-compressed data, including various items which are part of the project (.[[PNG|png]], .[[SVG|svg]], and .[[WAV|wav]] files, named with numbers). The main item is a file called '''project.json''', in [[JSON]] format. Detailed documentation can be found in the Scratch wiki. == Examples == Empty project (via the Scratch wiki): <pre> { "objName": "Stage", "costumes": [{ "costumeName": "backdrop1", "baseLayerID": 1, "baseLayerMD5": "739b5e2a2435f6e1ec2993791b423146.png", "bitmapResolution": 1, "rotationCenterX": 240, "rotationCenterY": 180 }], "currentCostumeIndex": 0, "penLayerMD5": "5c81a336fab8be57adc039a8a2b33ca9.png", "penLayerID": 0, "tempoBPM": 60, "videoAlpha": 0.5, "children": [], "info": { "userAgent": "Scratch 2.0 Offline Editor", "videoOn": false, "scriptCount": 0, "flashVersion": "WIN 32,0,0,182", "spriteCount": 0, "swfVersion": "v461" } } </pre> Default project (via the Scratch wiki): <pre> { "objName": "Stage", "sounds": [{ "soundName": "pop", "soundID": 1, "md5": "83a9787d4cb6f3b7632b4ddfebf74367.wav", "sampleCount": 258, "rate": 11025, "format": "" }], "costumes": [{ "costumeName": "backdrop1", "baseLayerID": 3, "baseLayerMD5": "739b5e2a2435f6e1ec2993791b423146.png", "bitmapResolution": 1, "rotationCenterX": 240, "rotationCenterY": 180 }], "currentCostumeIndex": 0, "penLayerMD5": "5c81a336fab8be57adc039a8a2b33ca9.png", "penLayerID": 0, "tempoBPM": 60, "videoAlpha": 0.5, "children": [{ "objName": "Sprite1", "sounds": [{ "soundName": "meow", "soundID": 0, "md5": "83c36d806dc92327b9e7049a565c6bff.wav", "sampleCount": 18688, "rate": 22050, "format": "" }], "costumes": [{ "costumeName": "costume1", "baseLayerID": 1, "baseLayerMD5": "f9a1c175dbe2e5dee472858dd30d16bb.svg", "bitmapResolution": 1, "rotationCenterX": 47, "rotationCenterY": 55 }, { "costumeName": "costume2", "baseLayerID": 2, "baseLayerMD5": "6e8bd9ae68fdb02b7e1e3df656a75635.svg", "bitmapResolution": 1, "rotationCenterX": 47, "rotationCenterY": 55 }], "currentCostumeIndex": 0, "scratchX": 0, "scratchY": 0, "scale": 1, "direction": 90, "rotationStyle": "normal", "isDraggable": false, "indexInLibrary": 1, "visible": true, "spriteInfo": { } }], "info": { "userAgent": "Scratch 2.0 Offline Editor", "videoOn": false, "scriptCount": 0, "flashVersion": "WIN 32,0,0,182", "spriteCount": 1, "swfVersion": "v461" } } </pre> == Documentation == * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(2.0) Scratch 2.0 File Format] == Other links == * [http://scratch.mit.edu/ Official Scratch site] == Other versions == * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(1.4) Scratch 1.4 File Format] * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(3.0) Scratch 3.0 File Format] [[Category:ZIP based file formats]] [[Category:JSON based file formats]] [[Category:MIT]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Scratch_2.0_File_Format Scratch 2.0 File Format 2025-04-18T13:57:14Z

Ross-spencer: Fixup link and provide other versions <hr /> <div>{{FormatInfo |subcat=Source code |extensions={{ext|sb2}}, {{ext|sprite2}} }} The '''Scratch 2.0 File Format''' saves projects in version 2.0 of the [[Scratch]] programming language. Scratch is a language designed to teach programming to young children. Since the program code consists of graphical tiles rather than text-based source code, a binary format was used for the earlier [[Scratch 1.4 File Format]], but the format has changed with 2.0. Scratch 2.0 runs from a web browser, so no installation is needed as with the earlier versions. Registered users can save their programs on the server, but unregistered users can still run Scratch online and upload/download programs saved on their own computer. Scratch projects are stored in files with a '''.sb2''' extension. The contents are [[ZIP]]-compressed data, including various items which are part of the project (.[[PNG|png]], .[[SVG|svg]], and .[[WAV|wav]] files, named with numbers). The main item is a file called '''project.json''', in [[JSON]] format. Detailed documentation can be found in the Scratch wiki. == Documentation == * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(2.0) Scratch 2.0 File Format] == Other links == * [http://scratch.mit.edu/ Official Scratch site] == Other versions == * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(1.4) Scratch 1.4 File Format] * [https://en.scratch-wiki.info/wiki/Scratch_File_Format_(3.0) Scratch 3.0 File Format] [[Category:ZIP based file formats]] [[Category:JSON based file formats]] [[Category:MIT]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/PKPass PKPass 2025-04-18T13:16:41Z

Ross-spencer: Add required fields <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Coupons and Tickets |extensions={{ext|pkpass}} |mimetypes={{mimetype|application/vnd.apple.pkpass}} }} '''PKPass''' is the format of tickets, coupons, and loyalty cards used in the iOS Passbook app (and other apps designed to use the format). It is a [[ZIP]]-format archive (but using the .pkpass extension instead of .zip) containing [[JSON]]-format data along with some [[PNG]]-format images. The files within the archive have specific expected names to denote their function. == pass.json Structure == The <code>pass.json</code> structure is described [https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/Creating.html here] and supported with reference files. The following fields are described as being required: * <code>passTypeIdentifier</code> * <code>serialNumber</code> * <code>formatVersion</code> * <code>teamIdentifier</code> * <code>organizationName</code> * <code>description</code> == Links == * [http://developer.apple.com/library/ios/#documentation/UserExperience/Reference/PassKit_Bundle/Chapters/Introduction.html#//apple_ref/doc/uid/TP40012026 Pass file format] * [http://developer.apple.com/library/ios/#documentation/UserExperience/Reference/PassKit_Bundle/Chapters/PackageStructure.html#//apple_ref/doc/uid/TP40012026-CH1-SW1 Package structure] (gives filenames to be used) * [http://developer.apple.com/library/ios/#documentation/PassKit/Reference/PKPass_Ref/PKPass.html PKPass class reference] * [https://play.google.com/store/apps/details?id=com.attidomobile.passwallet PassWallet for Android] == Examples links == * [https://reinteractive.com/articles/create-an-apple-wallet-pass-using-pass-json-file creating an apple pass file tutorial]. * [https://github.com/keefmoon/Passbook-Example-Code/blob/029e97b0dae29dee86bd4bafccc6639a71d8cd4c/Pass-Example-Generic/Pass-Example-Generic.pkpass generic pass example (zip)]. * [https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/YourFirst.html building your first pass on the apple developer network]. * [https://developer.apple.com/services-account/download?path=/iOS/Wallet_Support_Materials/WalletCompanionFiles.zip Pass Tutorial Companion Files (Auth required)]. [[Category:Apple]] [[Category:iOS]] [[Category:ZIP based file formats]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/PKPass PKPass 2025-04-18T13:10:12Z

Ross-spencer: Added example links <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Coupons and Tickets |extensions={{ext|pkpass}} |mimetypes={{mimetype|application/vnd.apple.pkpass}} }} '''PKPass''' is the format of tickets, coupons, and loyalty cards used in the iOS Passbook app (and other apps designed to use the format). It is a [[ZIP]]-format archive (but using the .pkpass extension instead of .zip) containing [[JSON]]-format data along with some [[PNG]]-format images. The files within the archive have specific expected names to denote their function. == Links == * [http://developer.apple.com/library/ios/#documentation/UserExperience/Reference/PassKit_Bundle/Chapters/Introduction.html#//apple_ref/doc/uid/TP40012026 Pass file format] * [http://developer.apple.com/library/ios/#documentation/UserExperience/Reference/PassKit_Bundle/Chapters/PackageStructure.html#//apple_ref/doc/uid/TP40012026-CH1-SW1 Package structure] (gives filenames to be used) * [http://developer.apple.com/library/ios/#documentation/PassKit/Reference/PKPass_Ref/PKPass.html PKPass class reference] * [https://play.google.com/store/apps/details?id=com.attidomobile.passwallet PassWallet for Android] == Examples links == * [https://reinteractive.com/articles/create-an-apple-wallet-pass-using-pass-json-file creating an apple pass file tutorial]. * [https://github.com/keefmoon/Passbook-Example-Code/blob/029e97b0dae29dee86bd4bafccc6639a71d8cd4c/Pass-Example-Generic/Pass-Example-Generic.pkpass generic pass example (zip)]. * [https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/YourFirst.html building your first pass on the apple developer network]. * [https://developer.apple.com/services-account/download?path=/iOS/Wallet_Support_Materials/WalletCompanionFiles.zip Pass Tutorial Companion Files (Auth required)]. [[Category:Apple]] [[Category:iOS]] [[Category:ZIP based file formats]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Piskel_canvas Piskel canvas 2025-04-18T12:40:09Z

Ross-spencer: Fixup example <hr /> <div> {{FormatInfo | name = Piskel canvas | formattype = electronic | subcat = Graphics | thiscat = | extensions = {{ext|piskel}} | mimetypes = {{mimetype|image/png+json}} | locfdd = | fourccs = | pronom = | type code = | uniform type = | wikidata = {{wikidata|Q101250905}} | compression = Always Lossless (from PNG) | extended from = [[JSON]], [[PNG]], [[base64]] | magic = | kaitai struct = | spec = | spec availability = free | reference impl = https://github.com/piskelapp/piskel | conforms to = {{UTI|JSON}} | charset = utf8 | charsetaliases = | codepage = | mibenum = | cfstringencoding = | nsstringencoding = | endianness = | tpm = | error resilience = | patent license = Unencumbered | developed by = Piskel | maintained by = Piskel | released = | image = | caption = | mime = | mime aliases = | version = | previous version = | next version = | back compat = | wikipedia = | container for = | contained by = | extended to = | embeddable metadata = filename, file description, file version | dependencies = | namespace = }} == Description == '''.piskel''' files are containers produced by the cross-platform Piskel graphics editor for still and animated pixel art. It is [[JSON]]-based and internally encodes the images or frames of the animated image as [[Base64|base-64d]] [[PNG]]s. == Information == * https://github.com/piskelapp/piskel == Software == * Piskel === Creation === * Piskel === Playback === * Piskel == Links == * https://piskelapp.com == Example == <pre> <nowiki> { "modelVersion": 1, "piskel": { "name": "example", "description": "exemplary", "fps": 12, "height": 32, "width": 32, "layers": [ "{\"name\":\"Layer 1\",\"opacity\":1,\"frameCount\":1,\"chunks\":[{\"layout\":[[0]],\"base64PNG\":\"data:image/png;base64,iVBORw0KGgoAAA\"}" ] } } </nowiki> </pre> [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Open_Web_App_Manifest Open Web App Manifest 2025-04-18T11:56:51Z

Ross-spencer: Provide more context for archive.org links <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|webapp}} |mimetypes={{mimetype|application/x-web-app-manifest+json}} }} An '''Open Web App''' is Mozilla's answer to the proprietary app stores. It is a website that has an acompanying manifest file which accomplishes such things as granting the "app" permission to access things on the user's device (such as contact lists) if it is properly installed, and giving it an icon which can be placed on a system desktop. When run, a web app behaves more like a native program than a website, even though it is actually being accessed on the web. These apps are supported by the Firefox browser on various platforms including Windows systems and Android mobile devices. Manifest files are in [[JSON]] format and given a '''.webapp''' extension. The MIME type of '''application/x-web-app-manifest+json''' is used (enforced by the Firefox Marketplace, though not by the browser itself). == Links and references == * [https://web.archive.org/web/20130806161912/https://developer.mozilla.org/en-US/docs/Web/Apps/Manifest App manifest docs (Mozilla) (Early archive.org reference)] * [https://web.archive.org/web/20210327233048/https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS/Manifest 2021 archive.org reference with more information about required fields] * [https://marketplace.firefox.com/ Firefox Marketplace] [[Category:JSON based file formats]] [[Category:Mozilla]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Open_Web_App_Manifest Open Web App Manifest 2025-04-18T11:49:43Z

Ross-spencer: Provide archive.org link <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|webapp}} |mimetypes={{mimetype|application/x-web-app-manifest+json}} }} An '''Open Web App''' is Mozilla's answer to the proprietary app stores. It is a website that has an acompanying manifest file which accomplishes such things as granting the "app" permission to access things on the user's device (such as contact lists) if it is properly installed, and giving it an icon which can be placed on a system desktop. When run, a web app behaves more like a native program than a website, even though it is actually being accessed on the web. These apps are supported by the Firefox browser on various platforms including Windows systems and Android mobile devices. Manifest files are in [[JSON]] format and given a '''.webapp''' extension. The MIME type of '''application/x-web-app-manifest+json''' is used (enforced by the Firefox Marketplace, though not by the browser itself). == Links and references == * [https://web.archive.org/web/20130806161912/https://developer.mozilla.org/en-US/docs/Web/Apps/Manifest App manifest docs (Mozilla)] * [https://marketplace.firefox.com/ Firefox Marketplace] [[Category:JSON based file formats]] [[Category:Mozilla]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/JSON_Table_Schema JSON Table Schema 2025-04-16T21:47:34Z

Ross-spencer: Add IA link <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''JSON Table Schema''' is a method, expressable in [[JSON]], of specifying the field structure of tabular data, for instance a spreadsheet or [[CSV]] file. It is "in competition" with [[CSV Schema]] as a way to describe a CSV data structure. It can be accompanied by a [[CSV Dialect Description Format]] file to describe the specifics of the delimiter and quoting rules in a CSV or other delimited file. == Links == * [http://dataprotocols.org/json-table-schema/ Official description/spec] * [https://web.archive.org/web/20230519194832/http://dataprotocols.org/json-table-schema/ official documentation on archive.org] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/HAR HAR 2025-04-16T20:13:23Z

Ross-spencer: /* Other links */ <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|har}}, {{ext|harp}} |released=2012 }} '''HAR''' (HTTP Archive) is a format based on [[JSON]] for saving a record of a Web access, including the [[HTTP]] request and response headers used to retrieve a document, and timing information on how long each part took to load. They can be used in server analysis and in archiving of Web data. HAR files are required to be encoded in the [[UTF-8]] character encoding. .har files are raw HAR, while .harp files are HAR enclosed in a callback function for use as [[JavaScript]] code. == Expected fields and objects == Within a <code>log</code> object: * version [string] * creator [object] * browser [object, optional] * pages [array, optional] * entries [array] * comment [string, optional] (new in 1.2) === Example === <pre> { "log": { "version": "1.2", "creator": {}, "browser": {}, "pages": [], "entries": [], "comment": "" } } </pre> == Specs == * [https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HAR/Overview.html Official spec, at W3C] * [http://www.softwareishard.com/blog/har-12-spec/ HAR 1.2 spec, at Software is hard] == Utilities == * [http://www.softwareishard.com/blog/har-viewer/ HAR viewer (Software is hard)] * [https://github.com/janodvarko/harviewer harviewer (GitHub)] ** [https://code.google.com/p/harviewer/ harviewer (Google Code)] * [http://ericduran.github.io/chromeHAR/ Chrome HAR viewer] == Other links == * [[Wikipedia:.har|Wikipedia article]] * [http://www.speedawarenessmonth.com/what-is-a-har-file-and-what-do-i-use-it-for/ What is a HAR File and what do I use it for?] * [https://gist.github.com/igrigorik/3495174 Example HAR Export] [[Category:Archiving]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/HAR HAR 2025-04-16T20:09:05Z

Ross-spencer: /* Expected fields and objects */ <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|har}}, {{ext|harp}} |released=2012 }} '''HAR''' (HTTP Archive) is a format based on [[JSON]] for saving a record of a Web access, including the [[HTTP]] request and response headers used to retrieve a document, and timing information on how long each part took to load. They can be used in server analysis and in archiving of Web data. HAR files are required to be encoded in the [[UTF-8]] character encoding. .har files are raw HAR, while .harp files are HAR enclosed in a callback function for use as [[JavaScript]] code. == Expected fields and objects == Within a <code>log</code> object: * version [string] * creator [object] * browser [object, optional] * pages [array, optional] * entries [array] * comment [string, optional] (new in 1.2) === Example === <pre> { "log": { "version": "1.2", "creator": {}, "browser": {}, "pages": [], "entries": [], "comment": "" } } </pre> == Specs == * [https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HAR/Overview.html Official spec, at W3C] * [http://www.softwareishard.com/blog/har-12-spec/ HAR 1.2 spec, at Software is hard] == Utilities == * [http://www.softwareishard.com/blog/har-viewer/ HAR viewer (Software is hard)] * [https://github.com/janodvarko/harviewer harviewer (GitHub)] ** [https://code.google.com/p/harviewer/ harviewer (Google Code)] * [http://ericduran.github.io/chromeHAR/ Chrome HAR viewer] == Other links == * [[Wikipedia:.har|Wikipedia article]] * [http://www.speedawarenessmonth.com/what-is-a-har-file-and-what-do-i-use-it-for/ What is a HAR File and what do I use it for?] [[Category:Archiving]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/HAR HAR 2025-04-16T20:04:26Z

Ross-spencer: Add expected fields <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|har}}, {{ext|harp}} |released=2012 }} '''HAR''' (HTTP Archive) is a format based on [[JSON]] for saving a record of a Web access, including the [[HTTP]] request and response headers used to retrieve a document, and timing information on how long each part took to load. They can be used in server analysis and in archiving of Web data. HAR files are required to be encoded in the [[UTF-8]] character encoding. .har files are raw HAR, while .harp files are HAR enclosed in a callback function for use as [[JavaScript]] code. == Expected fields and objects == * version [string] * creator [object] * browser [object, optional] * pages [array, optional] * entries [array] * comment [string, optional] (new in 1.2) == Specs == * [https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HAR/Overview.html Official spec, at W3C] * [http://www.softwareishard.com/blog/har-12-spec/ HAR 1.2 spec, at Software is hard] == Utilities == * [http://www.softwareishard.com/blog/har-viewer/ HAR viewer (Software is hard)] * [https://github.com/janodvarko/harviewer harviewer (GitHub)] ** [https://code.google.com/p/harviewer/ harviewer (Google Code)] * [http://ericduran.github.io/chromeHAR/ Chrome HAR viewer] == Other links == * [[Wikipedia:.har|Wikipedia article]] * [http://www.speedawarenessmonth.com/what-is-a-har-file-and-what-do-i-use-it-for/ What is a HAR File and what do I use it for?] [[Category:Archiving]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/CSV_Dialect_Description_Format CSV Dialect Description Format 2025-04-16T19:33:54Z

Ross-spencer: Delineate examples <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''CSV Dialect Dscription Format''' is a [[JSON]]-based format for describing the particular rules for a variety of delimited files, such as [[CSV]] or [[tab delimited]]. It does not describe the format of the data fields within a record of the file; this may be done with [[JSON Table Schema]] or [[CSV Schema]]. == Examples == === 1.0 === <pre> { "csvddf_version": 1.0, "dialect": { "delimiter": ",", "doublequote": false, "lineterminator": "\r\n", "quotechar": "\"", "skipinitialspace": false } } </pre> === 1.2 === <pre> { "csvddfVersion": 1.2, "delimiter": ",", "doubleQuote": true, "lineTerminator": "\r\n", "quoteChar": "\"", "skipInitialSpace": true, "header": true } </pre> == Links == * [http://dataprotocols.org/csv-dialect/ Official description/spec] * [https://web.archive.org/web/20131017022844/http://dataprotocols.org/csv-dialect/ Official description/spec via archive.org (v1.0)] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/CSV_Dialect_Description_Format CSV Dialect Description Format 2025-04-16T19:26:06Z

Ross-spencer: Provide JSON example <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''CSV Dialect Dscription Format''' is a [[JSON]]-based format for describing the particular rules for a variety of delimited files, such as [[CSV]] or [[tab delimited]]. It does not describe the format of the data fields within a record of the file; this may be done with [[JSON Table Schema]] or [[CSV Schema]]. == Examples == <pre> { "csvddf_version": 1.0, "dialect": { "delimiter": ",", "doublequote": false, "lineterminator": "\r\n", "quotechar": "\"", "skipinitialspace": false } } </pre> == Links == * [http://dataprotocols.org/csv-dialect/ Official description/spec] * [https://web.archive.org/web/20131017022844/http://dataprotocols.org/csv-dialect/ Official description/spec via archive.org (v1.0)] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/CSV_Dialect_Description_Format CSV Dialect Description Format 2025-04-16T19:20:00Z

Ross-spencer: Add IA link <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Schema formats }} '''CSV Dialect Dscription Format''' is a [[JSON]]-based format for describing the particular rules for a variety of delimited files, such as [[CSV]] or [[tab delimited]]. It does not describe the format of the data fields within a record of the file; this may be done with [[JSON Table Schema]] or [[CSV Schema]]. == Links == * [http://dataprotocols.org/csv-dialect/ Official description/spec] * [https://web.archive.org/web/20131017022844/http://dataprotocols.org/csv-dialect/ Official description/spec via archive.org (v1.0)] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/3D_Tiles 3D Tiles 2025-04-16T19:02:53Z

Ross-spencer: Add GitHub repository <hr /> <div>{{FormatInfo |subcat=3D and CAD/CAM Models |mimetypes={{mimetype|application/jsonl}} |extensions={{ext|json}} |pronom={{PRONOM|fmt/829}} |released=2016 }} '''3D Tiles''' is a [[JSON]]-based format designed for streaming and rendering geospatial data consisting of 3D objects organized in a hierarchical structure involving tilesets. The tiles may be of different sizes and are organized in a tree structure rather than a fixed grid. A right-handed Cartesian coordinate system is used to locate the objects. Various formats of data can be embedded as binary blobs. The [[glTF]] format is used as the basis of object models. ==Links== * [https://docs.ogc.org/cs/18-053r2/18-053r2.html 3D Tiles Spec 1.0] * [https://github.com/CesiumGS/3d-tiles/tree/main 3D Tiles GitHub] [[Category:Geospatial]] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Talk:Chrome_bookmarks Talk:Chrome bookmarks 2025-04-16T18:21:40Z

Ross-spencer: Question about format <hr /> <div>== Still JSON format? == Can anyone confirm a version of this where the format may have changed? If I download my bookmarks today it seems to be a HTML output. The oldest I have is 2014 and has the same header <code><!DOCTYPE NETSCAPE-Bookmark-file-1> </code> Perhaps once it was once JSON early on? (or reading the small-print, is it only JSON on-disk? (anyone know where that might be on Linux?) [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 18:21, 16 April 2025 (UTC)</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Jupyter_Notebook Jupyter Notebook 2025-04-16T17:43:31Z

Ross-spencer: Added Wikidata QID <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Scientific Data formats |extensions={{ext|ipynb}} |pronom={{PRONOM|fmt/1119}} |wikidata={{wikidata|Q105099901}} }} '''Jupyter Notebook''' is a FOSS web application for interactive notebook files that mix runnable code, explanatory text, and other multimedia. It is primarily used in the sciences, and has enjoyed popularity with the machine learning crowd. The Jupyter Notebook file format is [[JSON]]-based with extension .ipynb, after the project's predecessor, IPython. The format is open and [https://nbformat.readthedocs.io/en/latest/ exhaustively documented]. == External links == * [https://jupyter.org/ Official site] * [https://nbformat.readthedocs.io/en/latest/ Format documentation] [[Category:JSON based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/RO-CRATE RO-CRATE 2025-03-24T10:09:49Z

Ross-spencer: /* RO-CRATE file format */ <hr /> <div>{{FormatInfo |formattype=electronic |subcat= |extensions={{ext|jsonld}}{{ext|json}} |mimetypes={{mimetype|application/ld+json}} |pronom= |wikidata={{wikidata|Q124366860}} |released=2017 }} '''RO-CRATE''' ('''Research Object Crate''') is a packaging standard and metadata designed to describe research data and its inter-dependencies. == About == RO-CRATE specifies a metadata file that must use the filename <code>ro-crate-metadata.json</code>. The <code>ro-crate-metadata.json</code> file's presence in a directory identifies the root directory of a RO-CRATE object. The name of the containing directory is not fixed. Version 1.0 and before defined the root with a <code>.jsonld</code> extension, so: <code>ro-crate-metadata.jsonld</code>. RO-CRATE's metadata file describes data entries (files, directories) and contextual entities (licenses, authorship, funding, instrumentation, etc.). As linked data, the packaging format describes a graph of the package's content and its links to contextual information about its content. Its goal to enable reproducible, transparent, research. == RO-CRATE structure == The RO-CRATE package structure looks as follows. <pre> <RO-Crate root directory>/ | ro-crate-metadata.json # RO-Crate Metadata File MUST be present | ro-crate-preview.html # RO-Crate Website homepage MAY be present | ro-crate-preview_files/ # MAY be present | | [other RO-Crate Website files] | [payload files and directories] # 0 or more </pre> === RO-Crate Website homepage === Provides a human readable view of the RO-CRATE package. Tools exist to help support the creation of this file. == RO-CRATE specification == === Current version === [https://w3id.org/ro/crate/1.1 RO-CRATE 1.1] === Previous versions === [https://w3id.org/ro/crate/1.0 RO-CRATE 1.0] [https://w3id.org/ro/crate/0.2 RO-CRATE 0.2] === Draft version === [https://w3id.org/ro/crate/1.2-DRAFT RO-CRATE 1.2] == RO-CRATE file format == RO-CRATE's metadata file is built upon [[JSON]] and [[JSON-LD]]. The structure of the format provides a JSON-LD <code>@context</code> followed by a <code>@graph</code> of its data and contextual entities. The following example the RO-CRATE [https://www.researchobject.org/packaging_data_with_ro-crate/14-complete/index.html Packaging Data with RO-CRATE tutorial]. <pre> { "@context": "https://w3id.org/ro/crate/1.1/context", "@graph": [ { "@id": "ro-crate-metadata.json", "@type": "CreativeWork", "conformsTo": {"@id": "https://w3id.org/ro/crate/1.1"}, "about": {"@id": "./"} }, { "@id": "./", "@type": ["Dataset", "LearningResource"], "hasPart": [ {"@id": "data.csv"} ], "name": "Example dataset for RO-Crate specification", "description": "Official rainfall readings for Katoomba, NSW 2022, Australia", "datePublished": "2023-05-22T12:03:00+0100", "license": {"@id": "http://spdx.org/licenses/CC0-1.0"}, "author": { "@id": "https://orcid.org/0000-0002-1825-0097" }, "publisher": {"@id": "https://ror.org/05gq02987"} }, { "@id": "data.csv", "@type": "File", "name": "Rainfall Katoomba 2022-02", "description": "Rainfall data for Katoomba, NSW Australia February 2022", "encodingFormat": "text/csv", "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"} }, { "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/", "@type": "CreativeWork", "name": "CC BY-NC-SA 4.0 International", "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International" }, { "@id": "http://spdx.org/licenses/CC0-1.0", "@type": "CreativeWork", "name": "CC0-1.0", "description": "Creative Commons Zero v1.0 Universal", "url": "https://creativecommons.org/publicdomain/zero/1.0/" }, { "@id": "https://orcid.org/0000-0002-1825-0097", "@type": "Person", "name": "Josiah Carberry", "affiliation": { "@id": "https://ror.org/05gq02987" } }, { "@id": "https://ror.org/05gq02987", "@type": "Organization", "name": "Brown University", "url": "http://www.brown.edu/" } ] } </pre> Identifications based upon this structure might look for the appropriate context for a given version, and existence of the <code>@graph</code> array. === Minimal example === A minimal example of a RO-CRATE is described in the [https://www.researchobject.org/ro-crate/specification/1.1/root-data-entity.html#minimal-example-of-ro-crate spec]. <pre> { "@context": "https://w3id.org/ro/crate/1.1/context", "@graph": [ { "@type": "CreativeWork", "@id": "ro-crate-metadata.json", "conformsTo": {"@id": "https://w3id.org/ro/crate/1.1"}, "about": {"@id": "./"} }, { "@id": "./", "identifier": "https://doi.org/10.4225/59/59672c09f4a4b", "@type": "Dataset", "datePublished": "2017", "name": "Data files associated with the manuscript:Effects of facilitated family case conferencing for ...", "description": "Palliative care planning for nursing home residents with advanced dementia ...", "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/3.0/au/"} }, { "@id": "https://creativecommons.org/licenses/by-nc-sa/3.0/au/", "@type": "CreativeWork", "description": "This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Australia License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/au/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.", "identifier": "https://creativecommons.org/licenses/by-nc-sa/3.0/au/", "name": "Attribution-NonCommercial-ShareAlike 3.0 Australia (CC BY-NC-SA 3.0 AU)" } ] } </pre> == Example RO-CRATES == Links to examples can be found on the Research Object website: [https://www.researchobject.org/ro-crate/examples links to complete examples]. == Use Cases == RO-CRATE's use-cases are described on the [https://www.researchobject.org/ro-crate/use_cases RO-CRATE homepage]. Domain uses can be found under this page, ranging from Biology, to Chemistry, History, and Informatics. == Tools and libraries == * [https://github.com//language-research-technology RO-CRATE tooling from LDaCA] on GitHub. * [https://github.com/ResearchObject Tooling and specifications from the RO-CRATE community] on Github. * [https://language-research-technology.github.io/crate-o CRATE-O browser based editor] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE package preview generator] == Resources == * [https://www.researchobject.org/ RO-CRATE homepage] * [https://www.researchobject.org/ro-crate/specification RO-CRATE specification homepage] * [https://www.researchobject.org/ro-crate/dataverse Dataverse export of RO-CRATE] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE Preview (HTML) generation]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/User:Ross-spencer User:Ross-spencer 2025-02-26T17:06:36Z

Ross-spencer: Personal context <hr /> <div>Digital preservation specialist. Formerly: * The National Archives, UK (Digital Preservation Researcher), * Archives New Zealand (Digital Preservation Analyst), * Artefactual Systems Inc. (Software Developer), * Ravensburger AG (Digital Preservation Specialist), * Arkly.io (Senior Systems Architect). My background is in Software Development, Digital Humanities, and Digital Culture. Contact me via [https://twitter.com/beet_keeper Twitter] and find out more from my [http://exponentialdecay.co.uk/blog/ Blog] and [https://github.com/ross-spencer GitHub] pages. * [https://twitter.com/beet_keeper Twitter: @beet_keeper] * [http://exponentialdecay.co.uk/blog/ Personal Blog] * [https://github.com/exponential-decay GitHub: exponential-decay] and [https://github.com/ross-spencer GitHub: ross-spencer] My contributions to this wiki: * [http://fileformats.archiveteam.org/index.php?title=Special%3AContributions&tagfilter=&contribs=user&target=ross-spencer&namespace=&year=&month=-1 User Contributions]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/SOPS SOPS 2025-02-26T16:00:10Z

Ross-spencer: Add SOPS <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Encryption |extensions={{ext|yaml}} {{ext|json}} |mimetypes={{mimetype|application/json}} {{mimetype|application/yaml}} |pronom= |wikidata= |released=2016 }} '''SOPS'' ('''Secrets OPerationS''') is a structured format for managing secret keys. It belongs to the SOPS application ('''Simple and flexible tool for managing secrets''') and allows users to create encrypted key-value pairs for managing secrets. The utility is potentially helpful for development teams managing keys across projects. The primary formats that SOPS supports are <code>JSON</code> and <code>YAML</code>. == About == SOPS is initialized within your default editor using a key, e.g. PGP key. You can then proceed to create a data structure as you chose, the idea being, the keys in your structure will be encoded in plain-text once saved, and your values, again, once saved, will be encrypted. Similarly, decryption requires your keys to decode the SOPS structure back into the original data structure you began with. == Configuration and examples == === Test install === An example from the SOPS README shows how to test the utility using its example pgp key: <pre> git clone https://github.com/getsops/sops.git cd sops cd cmd go mod tidy go build gpg --import pgp/sops_functional_tests_key.asc </pre> === Example YAML === Given the above, you can then elect to edit a YAML file: <pre> ./sops edit example.yaml </pre> SOPS will bring up a default object, although this can be deleted and you can encode any structure. <pre> hello: Welcome to SOPS! Edit this file as you please!! example_key: example_value # Example comment example_array: - example_value1 - example_value2 example_number: 1234.56789 example_booleans: - true - false </pre> When this file is saved, values are wrapped with semantic information to help decoding, and a <code>'sops'</code> key created containing decode and encryption specific information. <pre> hello: ENC[AES256_GCM,data:uHToaQKhNuSRfJLfVPmBBAYzwDcA7OQ/gyd8AZqPtdAszHk4SevC6xA34x55tXU=,iv:M/ni78KR8us2zBf4myH+8QsivUyudM8DSKGdx0j7ltc=,tag:zECH/1665g+ebSu5HL0ppw==,type:str] example_key: ENC[AES256_GCM,data:MjFv3ewfpq1Sq+3WJg==,iv:NT/Yb3XawHuX/ypbzm9WPRLIar11Fq5uF0vJJtLgphY=,tag:wzlXdbtQBqmUpNcO3GQkng==,type:str] #ENC[AES256_GCM,data:HlTEj04aNP48sytIFPQhaQ==,iv:CWuWsTk7TmfFAyYUkwW/8xAv2XxY/bwwfCrayo5cCmE=,tag:CEpvfAM6PTZQHxhPv4f0ag==,type:comment] example_array: - ENC[AES256_GCM,data:4KxwWTHxEf3LDPx7UFc=,iv:l6caTOPmKxQFK+uREVzgezu2LbCyTEHTMu5bIJdm8+A=,tag:pjsY69yWWvbbGyqtAsPaUQ==,type:str] - ENC[AES256_GCM,data:vaTUurETsaYDJ6B1A5g=,iv:2UxiUDn6jWFyaZO8micUf/n98ELHLQYWzG74gpCVpy4=,tag:4NB/X0spcKHhbnOmYtZPZQ==,type:str] example_number: ENC[AES256_GCM,data:816+HcmStO0rpQ==,iv:VLXvtL9uLeylWLzvmXG/kKnxgzE8QuSmWqPGH6su4Fg=,tag:xxCmwfupJWjiO7jf4toHcA==,type:float] example_booleans: - ENC[AES256_GCM,data:vtkQiA==,iv:cxbZA3eecGy4XfF6rO2kI4ime9d7gKTqSPSz39tm9Fo=,tag:V71+rHj44N1tiu7uJlHiHg==,type:bool] - ENC[AES256_GCM,data:Cmv7aVs=,iv:FuyQn7wJrsPXRcloqtOq+PxNvY5DrCRISwGlUsVnmRQ=,tag:cJzDzUJavUbbcBapzQNh1g==,type:bool] sops: kms: [] gcp_kms: [] azure_kv: [] hc_vault: [] age: [] lastmodified: "2025-02-26T15:24:03Z" mac: ENC[AES256_GCM,data:iOigwJNFsPFZ2+hERTWE38izLH7QjiM/I+dxZLpEO8u0dkep/xh1BgtLHJMVspUisq4zI0XOwq4+ZTwpIOpC6yzaLt20X/2cLtWy5ZGlm3Vgo3iT0N7cbggKtXoSZ1XdzY9YP1bQl7grS8bnXYYeIKo5uJO517/nxydtaRYgJc0=,iv:rkE8ti+ZPTZnVlr8Aro32SfT9Lo3XDjUCOvbRqk5OHw=,tag:u5A+2ce1Ojmd6vnYHKm28Q==,type:str] pgp: - created_at: "2025-02-26T15:24:00Z" enc: |- -----BEGIN PGP MESSAGE----- hQEMAyUpShfNkFB/AQf/c7gcIWuhhsSfP9rd/ZAicTmh7+SM0GJhMR28snWBD/Sc sxYqZm+utqJW14Woi/XQUKrC7sanNguUNkCk6SKPKAWnQ+CjzaUlISbDyQwgKpQn eqr2q/5sFxWpFtzQpryK7lQzhIMbKhIKZh1xliLsL4Knkm2I7FO+KDBfVvJ9lwcR 4dBhXQdZySH4YNDT6Z7zK9o4cXswKa7OgoVHPVtqEHaDc2sA6GKBmrio3A9x5BAX xbf1r6FfT/XPFP1AlmV1Ixiu80lurfp39SuDfoHU7uVthrK7Oo9A7nd/Uu9zdS5O 7aPrbcSRtTN6ntglm3X/sU6oxgehVaTxipnW79XNntJeAXkFWLo5WMVCaIwXyenM uCfxeGd+fxL2k1miZC+7cXDorv5FfpAAQGURh3KbujHQ0n+ZriqW0wzYgweMSbFT skINiavro2+ocZXNrVZWWkexy2P8evcMWPVbVQ5HGw== =KkKj -----END PGP MESSAGE----- fp: FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4 - created_at: "2025-02-26T15:24:00Z" enc: |- -----BEGIN PGP MESSAGE----- hIwDXFUltYFwV4MBA/92mfagks7hCLfAGCuT2yFinvIheHTTfQn/sRHMkU4YsDDs 79fFtpAQRhiEe+2dcHP9QY4vNzk6G8yHnvSrpjkLlBz15F//2DTgPQGK0hutNo4n PMx+a99RSlvy2GJ/nSS2dBHJBj3JOt6iDk+eVzYQjDo4zjf+qeFm2m4QMkXqNNJe AY9AJ23ifr0tyhrlGbVd4KNcJmJLg6Vz3nxvG8r7TSLt91bTMUOi6owLkTFl+Tij X63YSoEauQzc/tSRKJfNFi5No173krsqXFQLyt2LrSPakZ0xgDGwU+fn2KCnmw== =Bj+H -----END PGP MESSAGE----- fp: D7229043384BCC60326C6FB9D8720D957C3D3074 unencrypted_suffix: _unencrypted version: 3.9.4 </pre> === Example JSON === Alternatively, you can elect to edit a JSON file: <pre> ./sops edit example.json </pre> SOPS will bring up a default object, although this can be deleted and you can encode any structure. <pre> { "hello": "Welcome to SOPS! Edit this file as you please!!", "example_key": "example_value", "example_array": [ "example_value1", "example_value2" ], "example_number": 1234.56789, "example_booleans": [ true, false ] } </pre> When this file is saved, values are wrapped with semantic information to help decoding, and a <code>'sops'</code> key created containing decode and encryption specific information. <pre> { "hello": "ENC[AES256_GCM,data:5t8seVgX/GxsD6muvKOnVgPjNk8yoX/Gbp3xCt0KuOH0yENKC0I6zyWUBgE0jIE=,iv:iPM4TVZ0GlQMZgEUWbGS+SHNVD0JF8uqT/X+VOij/dw=,tag:8Hnl4Giec2IcriApyc/CLA==,type:str]", "example_key": "ENC[AES256_GCM,data:LRMvnB36y2AvtrSbFw==,iv:kQ0LE2msZc50QHJhT+V84XbSiUA4yiynztJ/WvOVnFk=,tag:3hP8QJLPWezJ0lqiy7B+Vw==,type:str]", "example_array": [ "ENC[AES256_GCM,data:rENwn4lVjLQmb06OZo8=,iv:lI6HEkYkOmNavvMczUpc1QdE6sf4oZionB0EAk5o5TM=,tag:Niew51lQ87+JUMJQ0+Qpjw==,type:str]", "ENC[AES256_GCM,data:cxogL0GVCcgMA7D0bRY=,iv:zblA1Uo6FwYDkRj2RQ/Rv26lGY+Kcqy1IeDHyeJy/JQ=,tag:Pr9BIh1fG5cTKaZLJXuEGw==,type:str]" ], "example_number": "ENC[AES256_GCM,data:6l6Ez2VJm9AAsw==,iv:24bAR3EGZ+WHK0/4T+hB7/SLeVQ/8m3PsB5k6rYO0qY=,tag:ZVeEwIV0u4Mh48hf5kgjJg==,type:float]", "example_booleans": [ "ENC[AES256_GCM,data:sla9Gw==,iv:iMuyEFbO4GF5UkSiJY7eJeMd8TtCFtyHpzi0kbQMV60=,tag:nRUuew9bfSXLuZ4sKZr0Pg==,type:bool]", "ENC[AES256_GCM,data:LmA/l6U=,iv:M5QXLpIRMgH/RpJ6qlU+VtPytJUCT1RdE4FPsQ/WGyc=,tag:9nkIJHA9EQ+PMQVUUgyMSg==,type:bool]" ], "sops": { "kms": null, "gcp_kms": null, "azure_kv": null, "hc_vault": null, "age": null, "lastmodified": "2025-02-26T15:43:02Z", "mac": "ENC[AES256_GCM,data:0LWYLJbAbflAzS9URkFFAUzMtZCpqd8KnLQWYQLPJv5x8d9K9zNRh3meRX3PembwtZcr64IoVAJY3ft8Ttt6Dmww+UIhFQAvo8nmbDp3QVwUXzLgpFIodhNyUjSOm3Dj9ZVRXy5emHyd5Ai1ocQ7aUvN/Tj03Cb8DAw9Bf3Z+OU=,iv:S7edialcrk6AHV4UTedYXxVQpz342gpObFypzDdW3X4=,tag:CCpqLgKtnp1sqlgCVUrxnA==,type:str]", "pgp": [ { "created_at": "2025-02-26T15:42:52Z", "enc": "-----BEGIN PGP MESSAGE-----\n\nhQEMAyUpShfNkFB/AQf/XGtcWkKvKJX2Q5gky+ewG+BjIok6Ruw0Q5oebuawTgh0\nxHWN6miY/YSoq4jmz47u5QRYiPxfQ6kmeHYjbrkDJwkqev3dQ9e9X+Auk38W+EiT\nyDYxP9uML+d2GdG9irrHkeeMqZs7NPbohS2AQpT5NgA19PQB2PvwscMRZtOCjnEb\nTJcVZYkHQgXlLHJ6AdmNqneIwca6dN5x6pDnfys8oErK9bl5bsDAzm8LzOzIKHkf\nLKWRNyXkE2VBLjaTU431k7zXvG7F1BcA3BuaLhJaAPEkjg8wSy2H0Mx1fcTNoqfI\ncezuL+BUgNR0C2JVAzqgiP/92FADXl9NJpHCG+JzJdJcAdY8JIXqYcmJZqQYu82+\nNwykwnrdu6r/RWkDk0P+/u6GKVz6KCkAn5p9e45zs/z1fv1KfQMCM58w6fTEIdDW\n0sChyjEmxZq8wuu6c3xKxyCihVvL6SgIaY483zM=\n=794N\n-----END PGP MESSAGE-----", "fp": "FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4" }, { "created_at": "2025-02-26T15:42:52Z", "enc": "-----BEGIN PGP MESSAGE-----\n\nhIwDXFUltYFwV4MBA/wJkpY5y4wGupEEJKOwomPtCFDTCgn7ug3KFFMAbHm3lz6M\nd+a2CPr3jSEpyjE1VbLAWnxFpfoDTNzqOdWmCbwRkNCjV3ih9Y0SLVL0al/STz1T\nLQw99VN3IRMbTO9wbQ/OpyS+rodP4W/EmzHR5DQCqNH+8A/koWsjc1Fz/zIqC9Jc\nAQh0P381qCx5lbow8JaBmYZ9BE2qDmRC2uw0W8LYNP7sWAVxSXfwTqNV3YEtomnf\nQGGPnRKnGq3HrTgCKE9pAypYcCSariQEDV2aM6v8C5cfocVY6tco16qG2bg=\n=VpnI\n-----END PGP MESSAGE-----", "fp": "D7229043384BCC60326C6FB9D8720D957C3D3074" } ], "unencrypted_suffix": "_unencrypted", "version": "3.9.4" } } </pre> == Identification == It should be possible to create a signature from the SOPS data structure, looking for the <code>'sops'</code> key and some of the values encoded within there, e.g <code>'lastmodified'</code> and <code>'mac'</code> are two important values for the format. Additional details here, and understanding of the format will benefit signature research. == Links and references == * [https://getsops.io/ SOPS website] * [https://github.com/getsops/sops SOPS on GitHub] * [https://www.youtube.com/watch?v=V2PRhxphH2w Introduction tutorial on YouTube]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/RO-CRATE RO-CRATE 2025-02-07T11:36:57Z

Ross-spencer: Spelling <hr /> <div>{{FormatInfo |formattype=electronic |subcat= |extensions={{ext|jsonld}}{{ext|json}} |mimetypes={{mimetype|application/ld+json}} |pronom= |wikidata={{wikidata|Q124366860}} |released=2017 }} '''RO-CRATE''' ('''Research Object Crate''') is a packaging standard and metadata designed to describe research data and its inter-dependencies. == About == RO-CRATE specifies a metadata file that must use the filename <code>ro-crate-metadata.json</code>. The <code>ro-crate-metadata.json</code> file's presence in a directory identifies the root directory of a RO-CRATE object. The name of the containing directory is not fixed. Version 1.0 and before defined the root with a <code>.jsonld</code> extension, so: <code>ro-crate-metadata.jsonld</code>. RO-CRATE's metadata file describes data entries (files, directories) and contextual entities (licenses, authorship, funding, instrumentation, etc.). As linked data, the packaging format describes a graph of the package's content and its links to contextual information about its content. Its goal to enable reproducible, transparent, research. == RO-CRATE structure == The RO-CRATE package structure looks as follows. <pre> <RO-Crate root directory>/ | ro-crate-metadata.json # RO-Crate Metadata File MUST be present | ro-crate-preview.html # RO-Crate Website homepage MAY be present | ro-crate-preview_files/ # MAY be present | | [other RO-Crate Website files] | [payload files and directories] # 0 or more </pre> === RO-Crate Website homepage === Provides a human readable view of the RO-CRATE package. Tools exist to help support the creation of this file. == RO-CRATE specification == === Current version === [https://w3id.org/ro/crate/1.1 RO-CRATE 1.1] === Previous versions === [https://w3id.org/ro/crate/1.0 RO-CRATE 1.0] [https://w3id.org/ro/crate/0.2 RO-CRATE 0.2] === Draft version === [https://w3id.org/ro/crate/1.2-DRAFT RO-CRATE 1.2] == RO-CRATE file format == RO-CRATE's metadata file is built upon [[JSON]] and [[JSON-LD]]. The structure of the format provides a JSON-LD <code>@context</code> followed by a <code>@graph</code> of its data and contextual entities. The following example the RO-CRATE [https://www.researchobject.org/packaging_data_with_ro-crate/14-complete/index.html Packaging Data with RO-CRATE tutorial]. <pre> { "@context": "https://w3id.org/ro/crate/1.1/context", "@graph": [ { "@id": "ro-crate-metadata.json", "@type": "CreativeWork", "conformsTo": {"@id": "https://w3id.org/ro/crate/1.1"}, "about": {"@id": "./"} }, { "@id": "./", "@type": ["Dataset", "LearningResource"], "hasPart": [ {"@id": "data.csv"} ], "name": "Example dataset for RO-Crate specification", "description": "Official rainfall readings for Katoomba, NSW 2022, Australia", "datePublished": "2023-05-22T12:03:00+0100", "license": {"@id": "http://spdx.org/licenses/CC0-1.0"}, "author": { "@id": "https://orcid.org/0000-0002-1825-0097" }, "publisher": {"@id": "https://ror.org/05gq02987"} }, { "@id": "data.csv", "@type": "File", "name": "Rainfall Katoomba 2022-02", "description": "Rainfall data for Katoomba, NSW Australia February 2022", "encodingFormat": "text/csv", "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"} }, { "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/", "@type": "CreativeWork", "name": "CC BY-NC-SA 4.0 International", "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International" }, { "@id": "http://spdx.org/licenses/CC0-1.0", "@type": "CreativeWork", "name": "CC0-1.0", "description": "Creative Commons Zero v1.0 Universal", "url": "https://creativecommons.org/publicdomain/zero/1.0/" }, { "@id": "https://orcid.org/0000-0002-1825-0097", "@type": "Person", "name": "Josiah Carberry", "affiliation": { "@id": "https://ror.org/05gq02987" } }, { "@id": "https://ror.org/05gq02987", "@type": "Organization", "name": "Brown University", "url": "http://www.brown.edu/" } ] } </pre> Identifications based upon this structure might look for the appropriate context for a given version, and existence of the <code>@graph</code> array. == Example RO-CRATES == Links to examples can be found on the Research Object website: [https://www.researchobject.org/ro-crate/examples links to complete examples]. == Use Cases == RO-CRATE's use-cases are described on the [https://www.researchobject.org/ro-crate/use_cases RO-CRATE homepage]. Domain uses can be found under this page, ranging from Biology, to Chemistry, History, and Informatics. == Tools and libraries == * [https://github.com//language-research-technology RO-CRATE tooling from LDaCA] on GitHub. * [https://github.com/ResearchObject Tooling and specifications from the RO-CRATE community] on Github. * [https://language-research-technology.github.io/crate-o CRATE-O browser based editor] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE package preview generator] == Resources == * [https://www.researchobject.org/ RO-CRATE homepage] * [https://www.researchobject.org/ro-crate/specification RO-CRATE specification homepage] * [https://www.researchobject.org/ro-crate/dataverse Dataverse export of RO-CRATE] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE Preview (HTML) generation]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/RO-CRATE RO-CRATE 2025-02-07T11:26:15Z

Ross-spencer: Add links to examples <hr /> <div>{{FormatInfo |formattype=electronic |subcat= |extensions={{ext|jsonld}}{{ext|json}} |mimetypes={{mimetype|application/ld+json}} |pronom= |wikidata={{wikidata|Q124366860}} |released=2017 }} '''RO-CRATE''' ('''Research Object Crate''') is a packaging standard and metadata designed to describe research data and its inter-dependencies. == About == RO-CRATE specifies a metadata file that must use the filename <code>ro-crate-metadata.json</code>. The <code>ro-crate-metadata.json</code> file's presence in a directory identifies the root directory of a RO-CRATE object. The name of the containing directory is not fixed. Version 1.0 and before defined the root with a <code>.jsonld</code> extension, so: <code>ro-crate-metadata.jsonld</code>. RO-CRATE's metadata file describes data entries (files, directories) and contextual entities (licenses, authorship, funding, instrumentation, etc.). As linked data, the packaging format describes a graph of the package's content and its links to contextual information about its content. Its goal to enable reproducible, transparent, research. == RO-CRATE structure == The RO-CRATE package structure looks as follows. <pre> <RO-Crate root directory>/ | ro-crate-metadata.json # RO-Crate Metadata File MUST be present | ro-crate-preview.html # RO-Crate Website homepage MAY be present | ro-crate-preview_files/ # MAY be present | | [other RO-Crate Website files] | [payload files and directories] # 0 or more </pre> === RO-Crate Website homepage === Provides a human readable view of the RO-CRATE package. Tools exist to help support the creation of this file. == RO-CRATE specification == === Current version === [https://w3id.org/ro/crate/1.1 RO-CRATE 1.1] === Previous versions === [https://w3id.org/ro/crate/1.0 RO-CRATE 1.0] [https://w3id.org/ro/crate/0.2 RO-CRATE 0.2] === Draft version === [https://w3id.org/ro/crate/1.2-DRAFT RO-CRATE 1.2] == RO-CRATE file format == RO-CRATES file is built upon [[JSON]] and [[JSON-LD]]. The structure of the format provides a JSON-LD <code>@context</code> followed by a <code>@graph</code> of its data and contextual entities. The following example the RO-CRATE [https://www.researchobject.org/packaging_data_with_ro-crate/14-complete/index.html Packaging Data with RO-CRATE tutorial]. <pre> { "@context": "https://w3id.org/ro/crate/1.1/context", "@graph": [ { "@id": "ro-crate-metadata.json", "@type": "CreativeWork", "conformsTo": {"@id": "https://w3id.org/ro/crate/1.1"}, "about": {"@id": "./"} }, { "@id": "./", "@type": ["Dataset", "LearningResource"], "hasPart": [ {"@id": "data.csv"} ], "name": "Example dataset for RO-Crate specification", "description": "Official rainfall readings for Katoomba, NSW 2022, Australia", "datePublished": "2023-05-22T12:03:00+0100", "license": {"@id": "http://spdx.org/licenses/CC0-1.0"}, "author": { "@id": "https://orcid.org/0000-0002-1825-0097" }, "publisher": {"@id": "https://ror.org/05gq02987"} }, { "@id": "data.csv", "@type": "File", "name": "Rainfall Katoomba 2022-02", "description": "Rainfall data for Katoomba, NSW Australia February 2022", "encodingFormat": "text/csv", "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"} }, { "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/", "@type": "CreativeWork", "name": "CC BY-NC-SA 4.0 International", "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International" }, { "@id": "http://spdx.org/licenses/CC0-1.0", "@type": "CreativeWork", "name": "CC0-1.0", "description": "Creative Commons Zero v1.0 Universal", "url": "https://creativecommons.org/publicdomain/zero/1.0/" }, { "@id": "https://orcid.org/0000-0002-1825-0097", "@type": "Person", "name": "Josiah Carberry", "affiliation": { "@id": "https://ror.org/05gq02987" } }, { "@id": "https://ror.org/05gq02987", "@type": "Organization", "name": "Brown University", "url": "http://www.brown.edu/" } ] } </pre> Identifications based upon this structure might look for the appropriate context for a given version, and existence of the <code>@graph</code> array. == Example RO-CRATES == Links to examples can be found on the Research Object website: [https://www.researchobject.org/ro-crate/examples links to complete examples]. == Use Cases == RO-CRATE's use-cases are described on the [https://www.researchobject.org/ro-crate/use_cases RO-CRATE homepage]. Domain uses can be found under this page, ranging from Biology, to Chemistry, History, and Informatics. == Tools and libraries == * [https://github.com//language-research-technology RO-CRATE tooling from LDaCA] on GitHub. * [https://github.com/ResearchObject Tooling and specifications from the RO-CRATE community] on Github. * [https://language-research-technology.github.io/crate-o CRATE-O browser based editor] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE package preview generator] == Resources == * [https://www.researchobject.org/ RO-CRATE homepage] * [https://www.researchobject.org/ro-crate/specification RO-CRATE specification homepage] * [https://www.researchobject.org/ro-crate/dataverse Dataverse export of RO-CRATE] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE Preview (HTML) generation]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Siegfried Siegfried 2025-02-07T10:39:20Z

Ross-spencer: Add link to REST API <hr /> <div> {| |[[Software]] | > |[[File identification software]] | > | '''Siegfried''' |} Automated batch identification of file formats using internal and external signatures. Siegfried's primary signatures are derived from [[PRONOM]] and [[DROID]] but also has support for FreeDesktop.org's [https://freedesktop.org/wiki/Software/shared-mime-info/ MIME], Library of Congress' [http://www.digitalpreservation.gov/formats/fdd/descriptions.shtml FDD's], and [https://wikidata.org/ Wikidata]. == About == Like DROID, Siegfried supports identification of individual files, or entire directory trees. Siegfried can look within different aggregate file formats such as [[ZIP]], [[TAR]], [[WARC]] and [[ARC]]. Siegfried is open source and developed in Golang. Siegfied supports command-line output which can be piped into a file for further analysis. Siegfried's server support also offers access via [https://github.com/richardlehane/siegfried/wiki/Using-the-siegfried-server REST API]. Siegfried can also be [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm compiled as WASM] which enables client-side identification of file formats and client-side digital preservation workflows. == GitHub == Siegfried is [https://github.com/richardlehane/siegfried available on GitHub]. == Checksums == Siegfried supports `md5`, `sha1`, `sha256`, `sha512`, `crc` checksums. == Output formats == Siegfried supports output in YAML, JSON, CSV, and DROID compatible CSV. Siegfried also offers a replay capability to re-run existing signature files through its engine to convert the file to one of its other supported formats. == Customizing Siegfried == Siegfried can be customized through its partner application Roy. More information can be found on the [https://github.com/richardlehane/siegfried/wiki/Building-a-signature-file-with-ROY Roy Wiki]. === Wikidata === Folks may be interested in customizing the Wikidata signature file to get more fine-grained or specific results from Wikidata based identifications. The SPARQL source looks as follows: <pre> # Return all file format records from Wikidata. SELECT DISTINCT ?uri ?uriLabel ?puid ?extension ?mimetype ?encoding ?referenceLabel ?date ?relativity ?offset ?sig WHERE { { ?uri (wdt:P31/(wdt:P279*)) wd:Q235557. } UNION { ?uri (wdt:P31/(wdt:P279*)) wd:Q26085352. } FILTER(EXISTS { ?uri (wdt:P2748|wdt:P1195|wdt:P1163|ps:P4152) _:b2. }) FILTER((STRLEN(?sig)) >= 4 ) OPTIONAL { ?uri wdt:P2748 ?puid. } OPTIONAL { ?uri wdt:P1195 ?extension. } OPTIONAL { ?uri wdt:P1163 ?mimetype. } OPTIONAL { ?uri p:P4152 ?object. OPTIONAL { ?object pq:P3294 ?encoding. } OPTIONAL { ?object ps:P4152 ?sig. } OPTIONAL { ?object pq:P2210 ?relativity. } OPTIONAL { ?object pq:P4153 ?offset. } OPTIONAL { ?object prov:wasDerivedFrom ?provenance. OPTIONAL { ?provenance pr:P248 ?reference; pr:P813 ?date. } } } SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE], en". } } ORDER BY (?uri) </pre> [https://w.wiki/Cy4W Try It!] Once the SPARQL has been customized it can be used with Siegfried by following the instructions on the [https://github.com/richardlehane/siegfried/wiki/Wikidata-identifier#custom-wikibase Siegfried Wiki]. ==Related== {{Related file format identification}} == Resources == * [http://www.itforarchivists.com/siegfried Siegfried at IT for Archivists ] * [https://github.com/richardlehane/siegfried/wiki/ Siegfried Wiki] * [https://openpreservation.org/blogs/siegfried-pronom-based-file-format-identification-tool/ Siegfried â€“ a PRONOM-based, file format identification tool at the OPF] * [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm Siegfried WASM] * [https://www.digipres.org/publications/ipres/ipres-2021/papers/wikidata-a-magic-portal-for-siegfried-and-roy/ Wikidata: A Magic Portal for Siegfried and Roy] [[Category:File Format Identification]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Siegfried Siegfried 2025-02-07T10:38:26Z

Ross-spencer: /* Customizing Siegfried */ <hr /> <div> {| |[[Software]] | > |[[File identification software]] | > | '''Siegfried''' |} Automated batch identification of file formats using internal and external signatures. Siegfried's primary signatures are derived from [[PRONOM]] and [[DROID]] but also has support for FreeDesktop.org's [https://freedesktop.org/wiki/Software/shared-mime-info/ MIME], Library of Congress' [http://www.digitalpreservation.gov/formats/fdd/descriptions.shtml FDD's], and [https://wikidata.org/ Wikidata]. == About == Like DROID, Siegfried supports identification of individual files, or entire directory trees. Siegfried can look within different aggregate file formats such as [[ZIP]], [[TAR]], [[WARC]] and [[ARC]]. Siegfried is open source and developed in Golang. Siegfied supports command-line output which can be piped into a file for further analysis. Siegfried's server support also offers access via REST API. Siegfried can also be [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm compiled as WASM] which enables client-side identification of file formats and client-side digital preservation workflows. == GitHub == Siegfried is [https://github.com/richardlehane/siegfried available on GitHub]. == Checksums == Siegfried supports `md5`, `sha1`, `sha256`, `sha512`, `crc` checksums. == Output formats == Siegfried supports output in YAML, JSON, CSV, and DROID compatible CSV. Siegfried also offers a replay capability to re-run existing signature files through its engine to convert the file to one of its other supported formats. == Customizing Siegfried == Siegfried can be customized through its partner application Roy. More information can be found on the [https://github.com/richardlehane/siegfried/wiki/Building-a-signature-file-with-ROY Roy Wiki]. === Wikidata === Folks may be interested in customizing the Wikidata signature file to get more fine-grained or specific results from Wikidata based identifications. The SPARQL source looks as follows: <pre> # Return all file format records from Wikidata. SELECT DISTINCT ?uri ?uriLabel ?puid ?extension ?mimetype ?encoding ?referenceLabel ?date ?relativity ?offset ?sig WHERE { { ?uri (wdt:P31/(wdt:P279*)) wd:Q235557. } UNION { ?uri (wdt:P31/(wdt:P279*)) wd:Q26085352. } FILTER(EXISTS { ?uri (wdt:P2748|wdt:P1195|wdt:P1163|ps:P4152) _:b2. }) FILTER((STRLEN(?sig)) >= 4 ) OPTIONAL { ?uri wdt:P2748 ?puid. } OPTIONAL { ?uri wdt:P1195 ?extension. } OPTIONAL { ?uri wdt:P1163 ?mimetype. } OPTIONAL { ?uri p:P4152 ?object. OPTIONAL { ?object pq:P3294 ?encoding. } OPTIONAL { ?object ps:P4152 ?sig. } OPTIONAL { ?object pq:P2210 ?relativity. } OPTIONAL { ?object pq:P4153 ?offset. } OPTIONAL { ?object prov:wasDerivedFrom ?provenance. OPTIONAL { ?provenance pr:P248 ?reference; pr:P813 ?date. } } } SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE], en". } } ORDER BY (?uri) </pre> [https://w.wiki/Cy4W Try It!] Once the SPARQL has been customized it can be used with Siegfried by following the instructions on the [https://github.com/richardlehane/siegfried/wiki/Wikidata-identifier#custom-wikibase Siegfried Wiki]. ==Related== {{Related file format identification}} == Resources == * [http://www.itforarchivists.com/siegfried Siegfried at IT for Archivists ] * [https://github.com/richardlehane/siegfried/wiki/ Siegfried Wiki] * [https://openpreservation.org/blogs/siegfried-pronom-based-file-format-identification-tool/ Siegfried â€“ a PRONOM-based, file format identification tool at the OPF] * [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm Siegfried WASM] * [https://www.digipres.org/publications/ipres/ipres-2021/papers/wikidata-a-magic-portal-for-siegfried-and-roy/ Wikidata: A Magic Portal for Siegfried and Roy] [[Category:File Format Identification]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Talk:Electronic_File_Formats Talk:Electronic File Formats 2025-02-06T13:59:19Z

Ross-spencer: Question about research data <hr /> <div>There should probably be an agreed definition of an electronic file format to aid in selecting content and automating reasoning based on format IDs etc (if we are not all talking about the same things then we will not be able to generalise from the results of our work). What is an Electronic File format? Options: 1) a knowable, repeatable set of rules for structuring content in a computer file 2) a documented standard way of structuring computer files 3) the options that appear in the save-as drop-down menus in software applications 4) a file extension 5) a mime type 6) ??? ''preceeding question was written by [[User:Euanc|Euanc]].'' : For the moment, I can make this very simple. An Electronic File Format is a file format that can only be accessed through the use of electrical charge. The rest of what you're discussing is a matter of hierarchy below the "Electronic File Format" heading, which will definitely be sticky and hard to keep on top of, but can be done. --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 06:15, 1 November 2012 (UTC) : If an electronic file format is an "electronic" file format, then what is a file format? --[[User:Euanc|Euanc]] ([[User talk:Euanc|talk]]) 06:27, 1 November 2012 (UTC) :: See the article about "[[File Formats]]"; it uses that term in a more general way than it is normally used. --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 08:12, 19 January 2020 (UTC) : My own idea is that it is like 1 and 2. The others are designations of the formats rather than the formats itself. --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 08:09, 19 January 2020 (UTC) == ASN.1 == Is it a file format and if so, where should it go? [[Crusbridge]] :Hmm, I'd say it's a Domain Specific Language. I propose we add [[Domain Specific Language]] under [[Languages]]. Ideas, anyone? --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 03:15, 8 November 2012 (UTC) == Remaining uncategorized categories == I'm not sure where Resource Fork belongs; it's a platform-specific Mac thing, but is there some more general category it can be put in? It's kind of related to filesystems, so does it belong somewhere in that hierarchy? As for Binary Data, those can probably be moved to the specific category they belong in based on their function, like, is Multiplan a spreadsheet or something? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 14:17, 26 November 2012 (UTC) I also want to know where Magic Set Editor and TeXnicard file formats belong. These are programs used for making cards for card games such as Magic: the Gathering and others. Both programs can create a database of cards, export them to various formats, render the cards, and make statistics based on the cards, although their capabilities otherwise differ in many ways, and their file formats are also very different (and incompatible with each other, although it might be possible to use import/export templates in TeXnicard to convert from/to MSE format). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 08:09, 19 January 2020 (UTC) :[[Game data files]] maybe? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 14:18, 19 January 2020 (UTC) ::Maybe, although [[Game data files]] seems to be for computer games? --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 18:53, 19 January 2020 (UTC) :::There could be a subsection on that page for card games. The [[Saved Games]] page (another game-related category) has a board/card game section that includes bridge and chess. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 20:06, 19 January 2020 (UTC) == Addition of research Data == A research data category might be a useful subcategory to add. E.g. a type of file format or specification that can be applied across the natural sciences? e.g. the recent addition of [[RO-CRATE]]. [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 13:59, 6 February 2025 (UTC)</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Talk:RO-CRATE Talk:RO-CRATE 2025-02-06T13:57:30Z

Ross-spencer: Question about ro-crate-metadata.json <hr /> <div>== ro-crate-metadata.json == Do we have a name for it when specific naming conventions are used to describe data, e.g. here with <code>ro-crate-metadata.json</code>, we have magic nos. for bytes, do we have magic files for file names? [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 13:57, 6 February 2025 (UTC)</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/RO-CRATE RO-CRATE 2025-02-06T13:56:13Z

Ross-spencer: Add RO-CRATE <hr /> <div>{{FormatInfo |formattype=electronic |subcat= |extensions={{ext|jsonld}}{{ext|json}} |mimetypes={{mimetype|application/ld+json}} |pronom= |wikidata={{wikidata|Q124366860}} |released=2017 }} '''RO-CRATE''' ('''Research Object Crate''') is a packaging standard and metadata designed to describe research data and its inter-dependencies. == About == RO-CRATE specifies a metadata file that must use the filename <code>ro-crate-metadata.json</code>. The <code>ro-crate-metadata.json</code> file's presence in a directory identifies the root directory of a RO-CRATE object. The name of the containing directory is not fixed. Version 1.0 and before defined the root with a <code>.jsonld</code> extension, so: <code>ro-crate-metadata.jsonld</code>. RO-CRATE's metadata file describes data entries (files, directories) and contextual entities (licenses, authorship, funding, instrumentation, etc.). As linked data, the packaging format describes a graph of the package's content and its links to contextual information about its content. Its goal to enable reproducible, transparent, research. == RO-CRATE structure == The RO-CRATE package structure looks as follows. <pre> <RO-Crate root directory>/ | ro-crate-metadata.json # RO-Crate Metadata File MUST be present | ro-crate-preview.html # RO-Crate Website homepage MAY be present | ro-crate-preview_files/ # MAY be present | | [other RO-Crate Website files] | [payload files and directories] # 0 or more </pre> === RO-Crate Website homepage === Provides a human readable view of the RO-CRATE package. Tools exist to help support the creation of this file. == RO-CRATE specification == === Current version === [https://w3id.org/ro/crate/1.1 RO-CRATE 1.1] === Previous versions === [https://w3id.org/ro/crate/1.0 RO-CRATE 1.0] [https://w3id.org/ro/crate/0.2 RO-CRATE 0.2] === Draft version === [https://w3id.org/ro/crate/1.2-DRAFT RO-CRATE 1.2] == RO-CRATE file format == RO-CRATES file is built upon [[JSON]] and [[JSON-LD]]. The structure of the format provides a JSON-LD <code>@context</code> followed by a <code>@graph</code> of its data and contextual entities. The following example the RO-CRATE [https://www.researchobject.org/packaging_data_with_ro-crate/14-complete/index.html Packaging Data with RO-CRATE tutorial]. <pre> { "@context": "https://w3id.org/ro/crate/1.1/context", "@graph": [ { "@id": "ro-crate-metadata.json", "@type": "CreativeWork", "conformsTo": {"@id": "https://w3id.org/ro/crate/1.1"}, "about": {"@id": "./"} }, { "@id": "./", "@type": ["Dataset", "LearningResource"], "hasPart": [ {"@id": "data.csv"} ], "name": "Example dataset for RO-Crate specification", "description": "Official rainfall readings for Katoomba, NSW 2022, Australia", "datePublished": "2023-05-22T12:03:00+0100", "license": {"@id": "http://spdx.org/licenses/CC0-1.0"}, "author": { "@id": "https://orcid.org/0000-0002-1825-0097" }, "publisher": {"@id": "https://ror.org/05gq02987"} }, { "@id": "data.csv", "@type": "File", "name": "Rainfall Katoomba 2022-02", "description": "Rainfall data for Katoomba, NSW Australia February 2022", "encodingFormat": "text/csv", "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"} }, { "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/", "@type": "CreativeWork", "name": "CC BY-NC-SA 4.0 International", "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International" }, { "@id": "http://spdx.org/licenses/CC0-1.0", "@type": "CreativeWork", "name": "CC0-1.0", "description": "Creative Commons Zero v1.0 Universal", "url": "https://creativecommons.org/publicdomain/zero/1.0/" }, { "@id": "https://orcid.org/0000-0002-1825-0097", "@type": "Person", "name": "Josiah Carberry", "affiliation": { "@id": "https://ror.org/05gq02987" } }, { "@id": "https://ror.org/05gq02987", "@type": "Organization", "name": "Brown University", "url": "http://www.brown.edu/" } ] } </pre> Identifications based upon this structure might look for the appropriate context for a given version, and existence of the <code>@graph</code> array. == Use Cases == RO-CRATE's use-cases are described on the [https://www.researchobject.org/ro-crate/use_cases RO-CRATE homepage]. Domain uses can be found under this page, ranging from Biology, to Chemistry, History, and Informatics. == Tools and libraries == * [https://github.com//language-research-technology RO-CRATE tooling from LDaCA] on GitHub. * [https://github.com/ResearchObject Tooling and specifications from the RO-CRATE community] on Github. * [https://language-research-technology.github.io/crate-o CRATE-O browser based editor] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE package preview generator] == Resources == * [https://www.researchobject.org/ RO-CRATE homepage] * [https://www.researchobject.org/ro-crate/specification RO-CRATE specification homepage] * [https://www.researchobject.org/ro-crate/dataverse Dataverse export of RO-CRATE] * [https://www.npmjs.com/package/ro-crate-html RO-CRATE Preview (HTML) generation]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Siegfried Siegfried 2025-02-06T12:52:20Z

Ross-spencer: Add Siegfried as an identification tool <hr /> <div> {| |[[Software]] | > |[[File identification software]] | > | '''Siegfried''' |} Automated batch identification of file formats using internal and external signatures. Siegfried's primary signatures are derived from [[PRONOM]] and [[DROID]] but also has support for FreeDesktop.org's [https://freedesktop.org/wiki/Software/shared-mime-info/ MIME], Library of Congress' [http://www.digitalpreservation.gov/formats/fdd/descriptions.shtml FDD's], and [https://wikidata.org/ Wikidata]. == About == Like DROID, Siegfried supports identification of individual files, or entire directory trees. Siegfried can look within different aggregate file formats such as [[ZIP]], [[TAR]], [[WARC]] and [[ARC]]. Siegfried is open source and developed in Golang. Siegfied supports command-line output which can be piped into a file for further analysis. Siegfried's server support also offers access via REST API. Siegfried can also be [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm compiled as WASM] which enables client-side identification of file formats and client-side digital preservation workflows. == GitHub == Siegfried is [https://github.com/richardlehane/siegfried available on GitHub]. == Checksums == Siegfried supports `md5`, `sha1`, `sha256`, `sha512`, `crc` checksums. == Output formats == Siegfried supports output in YAML, JSON, CSV, and DROID compatible CSV. Siegfried also offers a replay capability to re-run existing signature files through its engine to convert the file to one of its other supported formats. == Customizing Siegfried == === Wikidata === Folks may be interested in customizing the Wikidata signature file to get more fine-grained or specific results from Wikidata based identifications. The SPARQL source looks as follows: <pre> # Return all file format records from Wikidata. SELECT DISTINCT ?uri ?uriLabel ?puid ?extension ?mimetype ?encoding ?referenceLabel ?date ?relativity ?offset ?sig WHERE { { ?uri (wdt:P31/(wdt:P279*)) wd:Q235557. } UNION { ?uri (wdt:P31/(wdt:P279*)) wd:Q26085352. } FILTER(EXISTS { ?uri (wdt:P2748|wdt:P1195|wdt:P1163|ps:P4152) _:b2. }) FILTER((STRLEN(?sig)) >= 4 ) OPTIONAL { ?uri wdt:P2748 ?puid. } OPTIONAL { ?uri wdt:P1195 ?extension. } OPTIONAL { ?uri wdt:P1163 ?mimetype. } OPTIONAL { ?uri p:P4152 ?object. OPTIONAL { ?object pq:P3294 ?encoding. } OPTIONAL { ?object ps:P4152 ?sig. } OPTIONAL { ?object pq:P2210 ?relativity. } OPTIONAL { ?object pq:P4153 ?offset. } OPTIONAL { ?object prov:wasDerivedFrom ?provenance. OPTIONAL { ?provenance pr:P248 ?reference; pr:P813 ?date. } } } SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE], en". } } ORDER BY (?uri) </pre> [https://w.wiki/Cy4W Try It!] Once the SPARQL has been customized it can be used with Siegfried by following the instructions on the [https://github.com/richardlehane/siegfried/wiki/Wikidata-identifier#custom-wikibase Siegfried Wiki]. ==Related== {{Related file format identification}} == Resources == * [http://www.itforarchivists.com/siegfried Siegfried at IT for Archivists ] * [https://github.com/richardlehane/siegfried/wiki/ Siegfried Wiki] * [https://openpreservation.org/blogs/siegfried-pronom-based-file-format-identification-tool/ Siegfried â€“ a PRONOM-based, file format identification tool at the OPF] * [https://github.com/richardlehane/siegfried/tree/063951c5773ce164f5bd1dadd504bdc8c22d8946/wasm Siegfried WASM] * [https://www.digipres.org/publications/ipres/ipres-2021/papers/wikidata-a-magic-portal-for-siegfried-and-roy/ Wikidata: A Magic Portal for Siegfried and Roy] [[Category:File Format Identification]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Eyeglass_file_format_(Ross_Spencer) Eyeglass file format (Ross Spencer) 2025-02-06T12:51:58Z

Ross-spencer: Add Wikidata and fix spelling <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Health and Medicine |extensions={{ext|eygl}} |wikidata={{wikidata|Q105858419}} }} The '''Eyeglass file format''' is an example file format developed by digital preservation researcher Ross Spencer to illustrate the process of creating file formats. It is not known to have been put to any actual use in the optical industry, but might be capable of doing so, as it encodes the standard pieces of information which are part of an eyeglass prescription. Spencer wrote a blog post explaining the choices that went into devising the file format, and created a Github site hosting some [[Python]] code and a sample data file. == File identification == Files begin with the hex bytes <code>BB 0D 0A 65 79 65 67 6C 61 73 73 1A 0A AB</code>, and ends with <code>BB 65 6f 66</code>. == Sample files == * [https://github.com/ross-spencer/eyeglass/blob/master/default-sample-1.0-be.eygl Official sample file] == Links == * [https://exponentialdecay.co.uk/blog/genesis-of-a-file-format/ Genesis of a file format] * [https://github.com/ross-spencer/eyeglass Github site] * [https://exponentialdecay.co.uk/blog/shattering-the-eyeglass/ Shattering the Eyeglass: Using Kaitai Structs to dissect the eyeglassâ€™ contents]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Just_Solve_the_File_Format_Problem:Community_portal Just Solve the File Format Problem:Community portal 2024-06-11T09:49:50Z

Ross-spencer: /* SSL and SEO */ <hr /> <div>: ''please add your signature by typing <nowiki>~~~~</nowiki> if you add or reply == Open issues == Below is a list of "issues" which would ordinarily be in a ticketing system of some kind, but are here on the Wiki instead, because that's how we roll. As things are resolved, they will be moved to the Discussion page. If there's an appeal or an issue, the conversation can continue there - this page will be for open issues. Use of case in URLS / links. I went through all the electronic format types pages, and tried to normalise all the pages where I could (there was a mix of link structures - I've tried to get them all (apart from animation - I've been at it all day!) so they are [[file extension]] - [[file type name]]. I notice that we have a mix of upper and lower case file extension through out. This means we may have 2 links which should point to the same URL (e.g. [[mix]] and [[MIX]]) is this a known issue with the current layout? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 01:32, 20 November 2012 (UTC) :Since you're linking both the extension and the name, does that mean that there are supposed to be separate articles for each? I don't know if there's really a need for "mainspace" articles by extension, since there are already categories for that purpose; you can browse them through [[:Category:File formats by extension]]. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:12, 20 November 2012 (UTC) ::I just copied the most common model that I found on the formats pages. The problem is, if you don't homogenize the method, the linking/crosslinking doesn't work properly. All instances of .doc (for example) should point to the same resource page / disambiguation page. If someone has linked to only format in one place (e.g. [[MS Word]] (.doc)), and someone else the extension (MS Word - [[doc]]), we can't makes sure they point to the same place. The problem occurs because format names and extensions are used interchangeably. You raise an interesting question about the relationship between the ext and the format name. I would argue they are not equal (1:1), nor (1:many) / (many:1) so it makes sense to protect both aspects as definable things - the extension because that's whats most commonly searched for and referred to by users and 'format name' because its more accurate. How is the [[:Category:File formats by extension]] populated? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 18:31, 20 November 2012 (UTC) :::The categories are inserted when you use the ext template in the infobox. My preference is to have articles by actual format name and use multiple navigation aids (menus, cats, etc.) to get to them. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:38, 21 November 2012 (UTC) == Article naming convention == As mentioned above, there's some dispute over whether to name articles after the full name of a format or its file extension. If using full names, you then get into issues of whether to use the full technical name or a shorter thing that's more popularly used, and in some cases that's even the same as the extension (GIF, for instance). And you also get into tricky issues of capitalization: all-caps like an acronym, all-lowercase like filenames are often done (though this is OS-dependent; some, like MS-DOS, use all-uppercase), or mixed case (proper names capitalized)? And then there's the disambiguation issue of how to name articles on different things that have the same name, which happens sometimes even with long official names, but even more often with short acronyms and file extensions. But there's also yet another issue of which things get separate articles and which are combined, like formats that have had many different versions, etc. Currently you have things like [[CI]] and [[CT]], recently-created articles that represent two different file types within the data of one type of music tracker. The spec document they link to is the same one, which documents all the file types used in that tracker. Unless there's going to be really a lot to say about each of the specific file types, my own preference would be to have one article called [[CyberTracker]] that discusses all the formats used by the program in question, with subheaders within the article for the different file types, and all the extensions listed in the infobox (and hence in associated categories). If any other indices by extension are built up, they'd also have entries for both CI and CT. For instance, when I documented [[Softdisk Family Tree]], I covered all the various file formats in one article, though there are several versions and multiple files for each. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:39, 21 November 2012 (UTC) : I realise I'm as guilty of this as anyone, having used both forms at some point (e.g. [[Surprise! Adlib Tracker v2.0]] and [[CI]]). Indeed, the two articles - [[CI]] and [[CT]] - you refer to were created by me. I guess in general I would favour using a descriptive page name rather than simply the file extension - that seems to be something that's being taken care of by infoboxes and categories. :On the issue of what gets a separate page and what doesn't, I guess that just comes down to individual discretion. There will be instances where a format has undergone a number of minor revisions over time or has a number of minor variants (e.g. the variant forms of Chaos Music Composer's [[CMC]]) where it would make sense to keep them all to a single page, while a major revision would necessitate a multi-page approach (e.g. the shift with Capella from the binary [[CAP]] to the XML-based [[CapXML]] format). :However, I'm not sure I agree with [[CI]] and [[CT]] having a single [[CyberTracker]] page. While both link to the same spec document and both are used by the same program, they are different formats serving different purposes. I think in general we should try and distinguish between program and file format - [[S3M]] doesn't belong on the [[ScreamTracker]] page, although each should link to the other. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 14:04, 21 November 2012 (UTC) :Since the purpose of the wiki is to document file formats, I think it's good that as many formats as possible are listed in the category pages and that you can browse these pages for format extensions. Sometimes it might be better to link multiple extension to the same article (e.g. a specific application), but not always. I think it is difficult to come up with a strict rule for this (but maybe recommendations and, even better, good examples). --[[User:PN|PN]] ([[User talk:PN|talk]]) 15:08, 21 November 2012 (UTC) ::It's a judgment call, certainly. It depends on how the files are typically encountered, distributed, used, etc., and how they're thought of by people who use them; if a bunch of file types related to a particular program are usually found together as part of a larger data set, they most likely belong together in one article (with subsections to describe the function of the particular files), but if they're distinct entities with their own particular treatment (like separate areas of file trading sites for enthusiasts) they should have separate articles, though more descriptive names like "CyberTracker instrument file" might be better than a cryptic and likely ambiguous CI. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:46, 21 November 2012 (UTC) ::And then, somebody has also used a robot to create pages in a separate namespace devoted to file extensions, like [[Ext:cin]]. That's yet another navigational system for getting to information by extension, though those pages oddly don't actually have direct links to the normal pages here about those file formats. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:56, 21 November 2012 (UTC) ::: Yes, that was me with Bender the bot. Still experimenting with it and working on creating a list of all pages in relation to extensions. [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 15:22, 22 November 2012 (UTC) ::What I'd like to avoid is the messy format somebody did to a few index pages like [[Compression]], where each line has separately hyperlinked format names and extensions (not always in a consistent order) where often one or the other is a redlink, or one redirects to the other, or one is just a disambiguation page, making a somewhat confusing hodgepodge. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:22, 21 November 2012 (UTC) :::I've started rearranging the Compression page to be a little less messy. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:56, 22 November 2012 (UTC) == So now what? == The official month of this project is now over... what are the plans for the site now? It's made a good start at documenting file formats, but has a good long way to go yet. (A project like this can never possibly be "finished", since there are always more file formats coming out of the woodwork, both new ones that are introduced, and old ones that are discovered.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 05:10, 1 December 2012 (UTC) : This is an awesome project and I will stay committed to it. Of course this first month is just a start. Let's roll people! [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 23:22, 3 December 2012 (UTC) == Anybody else still around? == Everybody else seems to have vanished around the middle of December... I'm the only one editing here lately. I hate to put more effort into improving a ghost town... anyone else even reading this? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 23:16, 2 January 2013 (UTC) : I will be editing more once I get back to work - still don't have a home internet connection and working from the local library computers / girlfriend's netbook over public wi-fi is a pain. It would be nice to see more contributions from others - you can see how much work is left to do on the music section alone, and I've really only been creating stub entries for most things. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:51, 3 January 2013 (UTC) :Well, I still stop by on occasion, and I've vowed to use the site as my first stop when I come across a file format I don't recognize, but I never made any substantial additions, so I'm not sure if that gives you any useful information. (My edits were mostly technical or editorial.) [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 00:18, 13 January 2013 (UTC) :I'll be editing from time-to-time. Currently a bit snowed under with other work, but planning to do more later in the year. Would also like to review the InfoBox(es) at some point, to ensure the information on this site can be reliably linked up to other information sources. [[User:AndyJackson|AndyJackson]] ([[User talk:AndyJackson|talk]]) 12:10, 18 January 2013 (UTC) :I'm here. Like Andy, my workload is quite high, but I'll be popping in and out. --[[User:Rhetoric X|Rhetoric X]] ([[User talk:Rhetoric X|talk]]) 12:31, 18 January 2013 (UTC) :I dip in and out when I want a challenge (or can stomach the frustration.) [[User:Foxtrot|Foxtrot]] ([[User talk:Foxtrot|talk]]) 11:47, 11 January 2023 (UTC) :Hi there! I sometimes add a word here or there. I must say this Wiki is pretty good now. Popular formats are nicely described and niche formats are just niche formats so it's sometimes hard to add anything about them. I think that maybe it would be helpful to start adding images to posts. An image explaining format details or a screenshot of an image editor may be a nice addition. What about algorithms in pseudo-code? --[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 0:28, 7 September 2018 (UTC) ::A description of file formats and pseudo-codes would be helpful (although you do not necessarily need a picture). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 05:19, 5 May 2019 (UTC) == Spam == I see the spammers have found the site, as I worried would happen; I run a wiki myself ([http://mpedia.dan.info/ MPedia], about things related to Mensa) and have to constantly play whack-a-mole with them; even adding such annoyances (for legitimate users) as a captcha and e-mail confirmation seem to only slightly slow the spammers down. I don't know the solution. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:59, 18 January 2013 (UTC) :...but "learn-to-read-Korean-in-15-minutes" is a legitimate addition, going to a comic strip explaining the [[Hangul]] writing system, which is in fact a legitimate article here since "file formats" is interpreted expansively to include human written languages. That link ''sounds'' a bit spammy, but if it was from a spammer, it would go to some page selling a dodgy language-learning tool, not a free-to-read resource! (It can start to get tricky distinguishing spam from legitimate stuff when you've got such a wide range of topics here to begin with! Once there's a huge flood of spam to get rid of, there's some danger of legitimate users getting caught in the net too.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:03, 18 January 2013 (UTC) ::Yes, it's incumbent on me to make sure we can have people sign up, and be a part of it, without getting spammers. We'll keep exploring. At least bots can't take us on.... I think.... --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 19:28, 18 January 2013 (UTC) :::If you've got some tips about how to configure MediaWiki to have open signups but not get the flood of spambots, let me know; that would help me with my own wiki. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:56, 22 January 2013 (UTC) == Orphaned / Blank Pages == I've been making an attempt to clear up some of the orphaned pages, but there are a few I'm not sure of - maybe Dan or someone could sort them out? * [[Emulation]] * [[FAQ:File Format]] * [[File format extensions list]] (seems to be used for the "ext:" pages but hasn't been updated) * [[Library]] * [[Original Plan]] * [[RAD Game Tools]] (should probably have the individual formats moved to appropriate sections) * [[Statistica]] (clearly belongs in Scientific Data formats, but I'm not sure where) I've also come across a few pages that should probably be deleted - either because they've been blanked at some point (I know I did this to a few pages) or because they contain data duplicated elsewhere. * [[AA]] * [[Compressed executable (.com)]] * [[SAP]] * [[Barnes & Noble Fixed-layout Format]] [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 10:41, 22 January 2013 (UTC) :OK, I deleted those last three; I'll look at the others. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:58, 22 January 2013 (UTC) :I put Statistica under "Mathematics" in the science category. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 22 January 2013 (UTC) Hi Dan, got another one for you - I merged the info from [[ODS files created by Microsoft Office 2007 SP2]] into the main [[OpenDocument Spreadsheet]] page. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:59, 25 February 2013 (UTC) Added Barnes & Noble to the list (made a bit of a mess and forgot about the rename feature) [[User:Johanvanderknijff|Johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 19:05, 21 April 2016 (UTC) == Permissions for user pages == Is there any way we can get permission to delete sub-pages of our own user pages? I've been using mine to draft articles bit by bit, rather than release half-finished articles into the wild, and it would be nice to be able to remove the drafts once complete [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 12:43, 3 October 2013 (UTC) :I'm not sure, but as an admin I can delete anything you ask. It might also be possible to use the Move function to move it directly into the intended place. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:45, 3 October 2013 (UTC) == cd.textfiles.com == All the files on http://cd.textfiles.com/ disappeared a few days ago, breaking about a million links on this wiki. Does anyone have any information about that? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 18:48, 25 January 2015 (UTC) :As I recall from Jason's Twitter feed, he had some server problems, with most of his sites going down at least temporary, and most of them eventually coming back up, but maybe that one had a harder crash. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:50, 25 January 2015 (UTC) == Broken image in footer == The "Creative Commons 0" image at the bottom of every page (https://www.mediawiki.org/w/skins/common/images/cc-0.png) is broken. Can that be fixed? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:06, 10 July 2015 (UTC) :Still broken 5 years later... Is this place even maintained? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 23:23, 12 March 2021 (UTC) ::Ok so it appears it should probably be [https://licensebuttons.net/l/zero/1.0/88x31.png this image], it matches the 88x31px that the HTML claims the image would be if it was there. Who maintains this site so it can be fixed? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 00:01, 13 March 2021 (UTC) :::I guess that would be Jason Scott. I'm an admin, but if I have any ability to edit that part of the site I have no idea how. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:31, 13 March 2021 (UTC) == Wikipedia links == At least in my geographical area, Wikipedia has been redirecting "http:" links to "https:". So, all of the <nowiki>[[Wikipedia:...]]</nowiki> links in this wiki are getting redirected. Could/should we change these links to use "https:" directly? The magic "RFC" links like RFC 822 could also use https:, though the http: links still work. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:10, 10 July 2015 (UTC) == Google Code == We still have around 50 articles that link to Google Code. My understanding is that the next phase of Google Code's shutdown process will happen on 2016-01-25 (two weeks from today). It would be good to update as many of these as possible before then. * [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=http%3A%2F%2Fcode.google.com&namespace= links to http://code.google.com] * [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fcode.google.com&namespace= links to https://code.google.com] [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:05, 11 January 2016 (UTC) == Cleanup of top-level categories == (Call for objections.) I want to do some cleanup of the [[:Category:Top Level Categories|top-level categories]], and make sure there's at least one category for virtually every article. (See [[Special:UncategorizedPages]].) My plans: * A new "Meta" category, for articles about the File Formats Wiki (e.g. [[FAQ]], [[Original Plan]], [[Statement of Project]], [[Main Page]], ...). * Rename the [[:Category:Geek humor|Geek humor]] category to "Humor" * Remove the [[:Category:Computer facts|Computer facts]] category * A new "Information" category, for relevant informative articles ([[Ontology]], [[Patents]], ...) that don't have a more suitable top-level category. * Maybe someday: A category named "Devices", or "Hardware", or even "Things". Most computers and [[Networked devices]] just aren't formats, IMHO. (But I'm not going to delete the infobox from all the "Networked devices" articles. If we can't figure out a way to have infoboxes for nonformats, then I'll leave them be.) [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 15:56, 1 June 2017 (UTC) [[Category:Meta]] == Love It! == Hi there, kudos to all you guys who helped create this valuable resource. Wikipedia is such a snob when it comes to detailed technical documentation so this wiki is a lifesaver. I added a few things to: * [[SWF#Software]] * [[FLA#Software]] * [[BSON#Libraries]] Thanks again! PS: Can the "thumbs up" icon be changed to something better? Do you want me to design a possible logo? [[User:Hgupta|Hgupta]] ([[User talk:Hgupta|talk]]) 05:42, 17 August 2017 (UTC) :Nice work! As for the thumb icon, you'd have to ask Jason Scott, the owner of this site (and the one who put the thumb up). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 17 August 2017 (UTC) :I support the idea of changing the logo. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:08, 18 August 2017 (UTC) == What time is it? == I'm making this edit at 17:10 UTC, but the timestamp is: [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 17:25, 2 May 2018 (UTC) :"Does anybody really know what time it is; does anybody really care?" -- Chicago [posted at 01:20 UTC; let's see when it thinks it is] [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:36, 3 May 2018 (UTC) == Type / Creator codes == Curious what everyone's thoughts are on collecting Type/Creator Codes for Macintosh formats. There seems to be a few attempts at doing this around the webs. Is there a way here to gather them all into one area of the wiki? --[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 17:46, 4 May 2019 (UTC) * [[Wikipedia:Type_code|Type Code : Wikipedia]] * [[Wikipedia:Creator_code|Creator Code : Wikipedia]] * [http://www.lacikam.co.il/tcdb/ TCDBx unmaintained] * [https://vintageapple.org/macprogramming/pdf/The_Programmers_Apple_Mac_Sourcebook_1989.pdf The Programmers Apple Mac Sourcebook] * [https://www.macdisk.com/macsigen.php Mac Signatures] :Maybe do it similar to how file extensions are handled, as an item in the infobox that links to a category? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:09, 4 May 2019 (UTC) ::An article for Mac type/creator codes has been on my to-do list for a while, so we could at least do that, and see if there's any interest in listing lots of codes there. Should it be one article, or two? FormatInfo already has a "type code" param that is supposed to be for the Mac code. Maybe we are supposed to make a "Type Code" template to go along with it, so we can do like "<nowiki>|type code={{Type Code|XXXX}}</nowiki>". [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:07, 4 May 2019 (UTC) :::If they were listed in a single article as opposed to a series of categories, I don't see what there would be for a template would do. In that case, the text on the left side of the infobox could link to the list page (although this might be ugly). (It would be convenient if there was something between the complexity of the MediaWiki category system and a list page, but I don't think anything like that exists in a plain Mediawiki installation.) [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:30, 4 May 2019 (UTC) ::Even if they went into the infobox, the category system could potentially be left out out, as is currently done with FOURCCs and MIMETypes (the latter links to an external database, but whether anything is there is based on luck more than anything else, as there are so many unregistered mimetypes). These can still be found with the wiki's search feature. [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:13, 4 May 2019 (UTC) :::And there's also the Creator Code, as noted above; that refers to what program created the file, so there might be several associated with one file type code (and several file type codes associated with one creator). Perhaps there needs to be a section of the article listing all the code values associated with a given format and/or program (depending on what's covered by the article). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 21:44, 4 May 2019 (UTC) ::I like the idea of at least a uniform template for using codes within format descriptions. Since most of the files from the early macintosh days don't have an extension, unless they were cross platform and the Windows extension is used, then the only way to identify the file is from its Type/Creator code. I don't think Apple ever released the full registry, but some estimates are well over 50,000 entries.--[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 03:24, 5 May 2019 (UTC) == Reverse engineering formats == I am trying to reverse engineer some formats. Sometimes successfully, sometimes not. My most recent attempt is: * http://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic) Maybe we can do this together instead of everyone here focusing on different things? Also is there a better way to discuss things than writing here? [[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 01:39, 9 May 2019 (UTC) :You should set up a NNTP for reverse engineering file formats discussions (if there isn't already the appropriaate newsgroup). (I had done some of my own reverse engineering file formats too, but I have not set up a NNTP to discuss them. I do have a NNTP server, so you can suggest newsgroups there if wanted, I suppose) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:26, 23 August 2021 (UTC) == CAPTCHA == AT is no longer on EFnet: https://archiveteam.org/index.php?title=Archiveteam:IRC#Special_ArchiveTeam_IRC_rules [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC) : This is a pretty serious problem. Are there any plans to fix it? -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:22, 12 November 2020 (UTC) :: <del>Seems like it has been fixed, by removing the CAPTCHA altogether.</del> [2021-12-30 edit: I spoke too soon; still 'efnet'.] Let's all keep a keen eye out for spamdalism. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 03:33, 23 November 2020 (UTC) == [[special:interwiki]] == don't see it at [[special:specialpages]]? [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC) : Perhaps the [https://www.mediawiki.org/wiki/Extension:Interwiki Interwiki extension] is not installed? â€”&nbsp;[[User:Rjt|rjt]]&nbsp;([[User talk:Rjt|talk]]) 15:16, 30 December 2023 (UTC) == List of my idea what maybe should be added on == My idea of what things I think that probably should be added on (when someone has the information of it to add): * TRON character encoding * TRON Application Databus * BANCStar * C67 (music) (I might add a few others later if I will remember some more later, too) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 09:30, 31 July 2021 (UTC) ==Hello== Iâ€™ve joined and made a few edits. Starting with the Linux page by modification of the attribution of Linux to iOS, which is BSD. Mad a few tweaks to HLP by creating a page for the source file. As a retro tech enthusiast I think I could help a bit on some of the older files. Especially tape and disk formats; then, and their modern emulation files. As well as format info. You can take a look at the original writeup I did here [http://wiki.digital-digest.com/index.php?title=History_of_AV]. Thought it has errors and is considerably lacking many formats. ==SSL and SEO== SSL has been a factor in web site indexing for a while https://security.googleblog.com/2014/08/https-as-ranking-signal_6.html. Anecdotally I am seeing this more profoundly with personal websites. I wonder if Just Solved can be upgraded to HTTPS sometime in the near future. This should help SEO rankings which benefits us all as it attracts more users. It also protects us using the site too. [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 07:34, 3 January 2023 (UTC) :You'd have to ask Jason about this server-level stuff. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:16, 3 January 2023 (UTC) :Please do not make TLS mandatory. However, optional TLS is a good idea. --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:13, 5 January 2023 (UTC) :NB. SSL is listed with further rationale in the TODO: http://fileformats.archiveteam.org/wiki/JustSolve:To_Do [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 09:49, 11 June 2024 (UTC) ==Mediawiki version== What are the plans to upgrade this site? Wikimedia is currently at 1.38, Just Solved File Formats is 1.19 with it's dependencies MySQL and PHP somewhat far behind current standards too. [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 07:34, 3 January 2023 (UTC) :Over the past six weeks, I've sent a few emails to Jason Scott asking how we could get some maintenance for this site. Although he has replied, with some indication that he might be willing to help, I haven't been able to figure out the right thing to say to make that actually happen. At this point, I'm not optimistic that my emails will be sufficient. -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 14:48, 25 February 2023 (UTC)</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Eyeglass_file_format_(Ross_Spencer) Eyeglass file format (Ross Spencer) 2023-11-06T13:47:44Z

Ross-spencer: Added the most recent blog about this format <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Health and Medicine |extensions={{ext|eygl}} }} The '''Eyeglass file format''' is an example file format developed by digital preservation researcher Ross Spencer to illustrate the process of creating file formats. It is not known to have been put to any actual use in the optical industry, but might be capable of doing so, as it encodes the standard pieces of information which are part of an eyeglass prescription. Spencer wrote a blog post explaining the choices that went into devising the file format, and created a Github site hosting some [[Python]] code and a sample data file. == File indentification == Files begin with the hex bytes <code>BB 0D 0A 65 79 65 67 6C 61 73 73 1A 0A AB</code>, and ends with <code>BB 65 6f 66</code>. == Sample files == * [https://github.com/ross-spencer/eyeglass/blob/master/default-sample-1.0-be.eygl Official sample file] == Links == * [https://exponentialdecay.co.uk/blog/genesis-of-a-file-format/ Genesis of a file format] * [https://github.com/ross-spencer/eyeglass Github site] * [https://exponentialdecay.co.uk/blog/shattering-the-eyeglass/ Shattering the Eyeglass: Using Kaitai Structs to dissect the eyeglassâ€™ contents]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Eyeglass_file_format_(Ross_Spencer) Eyeglass file format (Ross Spencer) 2023-10-20T22:32:55Z

Ross-spencer: Updated http to https <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Health and Medicine |extensions={{ext|eygl}} }} The '''Eyeglass file format''' is an example file format developed by digital preservation researcher Ross Spencer to illustrate the process of creating file formats. It is not known to have been put to any actual use in the optical industry, but might be capable of doing so, as it encodes the standard pieces of information which are part of an eyeglass prescription. Spencer wrote a blog post explaining the choices that went into devising the file format, and created a Github site hosting some [[Python]] code and a sample data file. == File indentification == Files begin with the hex bytes <code>BB 0D 0A 65 79 65 67 6C 61 73 73 1A 0A AB</code>, and ends with <code>BB 65 6f 66</code>. == Sample files == * [https://github.com/ross-spencer/eyeglass/blob/master/default-sample-1.0-be.eygl Official sample file] == Links == * [https://exponentialdecay.co.uk/blog/genesis-of-a-file-format/ Genesis of a file format] * [https://github.com/ross-spencer/eyeglass Github site]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/H2database H2database 2023-09-17T15:30:51Z

Ross-spencer: Add some information about versioning <hr /> <div>{{FormatInfo |subcat=Databases |extensions={{ext|db}} |mimetypes= |pronom= }} '''h2database''' (H2) is an open source JAVA SQL database that can be used as an embedded, server, or in-memory database. == Embedded format == H2's embedded format is a [https://www.h2database.com/html/mvstore.html#fileFormat MVStore file]. An example header is as follows: <pre> 00000000: 48 3a 32 2c 62 6c 6f 63 6b 3a 33 2c 62 6c 6f 63 H:2,block:3,bloc 00000010: 6b 53 69 7a 65 3a 31 30 30 30 2c 63 68 75 6e 6b kSize:1000,chunk 00000020: 3a 37 2c 63 72 65 61 74 65 64 3a 31 38 61 39 66 :7,created:18a9f 00000030: 61 34 64 65 35 39 2c 66 6f 72 6d 61 74 3a 32 2c a4de59,format:2, 00000040: 76 65 72 73 69 6f 6e 3a 37 2c 66 6c 65 74 63 68 version:7,fletch 00000050: 65 72 3a 33 35 34 65 34 38 65 31 0a 00 00 00 00 er:354e48e1..... </pre> From the documentation: <blockquote> There are two file headers, which normally contain the exact same data. But once in a while, the file headers are updated, and writing could partially fail, which could corrupt a header. That's why there is a second header. Only the file headers are updated in this way (called "in-place update"). The headers contain the following data: </blockquote> <blockquote> The data is stored in one file. The file contains two file headers (for safety), and a number of chunks. The file headers are one block each; a block is 4096 bytes. </blockquote> The fields are broken down in version 1 of the docs as follows: * H: The entry "H:2" stands for the H2 database. * block: The block number where one of the newest chunks starts (but not necessarily the newest). * blockSize: The block size of the file; currently always hex 1000, which is decimal 4096, to match the * * disk sector length of modern hard disks. * chunk: The chunk id, which is normally the same value as the version; however, the chunk id might roll over to 0, while the version doesn't. * created: The number of milliseconds since 1970 when the file was created. * format: The file format number. Currently 1. * version: The version number of the chunk. * fletcher: The Fletcher-32 checksum of the header. === Versioning === From the developer [https://github.com/h2database/h2database/issues/3892#issuecomment-1722484540], the versioning doesn't map 1:1 onto major releases. It maps as follows: <blockquote> No, it doesn't. Historic version of H2 (1.4.200 and older) use format 1, H2 2.0.* and 2.1.* use format 2, H2 2.2.* uses format 3. You cannot read actual version of H2 from headers of MVStore files, MVStore doesn't preserve it, only H2 does. </quote> Format signature development therefore might be as granular as overall "version" but it won't map to specific software. === Additional files in H2's persistent implementation === H2's database objects are described as follows. It may be important to identify these together in a preservation context but the documentation is unclear as to whether the database file can be interpreted in its own right. {| ! File Name ! Description ! Number of Files |- | test.mv.db | Database file. Contains the transaction log, indexes, and data for all tables. Format: <database>.mv.db | 1 per database |- | test.newFile | Temporary file for database compaction. Contains the new MVStore file. Format: <database>.newFile | 0 or 1 per database |- | test.tempFile | Temporary file for database compaction. Contains the temporary MVStore file. Format: <database>.tempFile | 0 or 1 per database |- | test.lock.db | Database lock file. Automatically (re-)created while the database is in use. Format: <database>.lock.db | 1 per database (only if in use) |- | test.trace.db | Trace file (if the trace option is enabled). Contains trace information. Format: <database>.trace.db Renamed to<database>.trace.db.old if too big. | 0 or 1 per database |- | test.123.temp.db | Temporary file. Contains a temporary blob or a large result set. Format: <database>.<id>.temp.db | 1 per object |- |} == Use in digital preservation == Fedora 6.0's webapp is backed by a H2 database by default. == Further information == * [https://h2database.com/html/main.html H2 database documentation] * [https://github.com/fcrepo/fcrepo fcrepo] * [https://wiki.lyrasis.org/display/FEDORA6x/Properties fcrepo database configuration] * [https://github.com/h2database/h2database/issues/3892 GitHub issue asking for more information about format mapping] [[category:File formats with extension .db]] [[category:SQL]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/H2database H2database 2023-09-17T10:42:29Z

Ross-spencer: <hr /> <div>{{FormatInfo |subcat=Databases |extensions={{ext|db}} |mimetypes= |pronom= }} '''h2database''' (H2) is an open source JAVA SQL database that can be used as an embedded, server, or in-memory database. == Embedded format == H2's embedded format is a [https://www.h2database.com/html/mvstore.html#fileFormat MVStore file]. An example header is as follows: <pre> 00000000: 48 3a 32 2c 62 6c 6f 63 6b 3a 33 2c 62 6c 6f 63 H:2,block:3,bloc 00000010: 6b 53 69 7a 65 3a 31 30 30 30 2c 63 68 75 6e 6b kSize:1000,chunk 00000020: 3a 37 2c 63 72 65 61 74 65 64 3a 31 38 61 39 66 :7,created:18a9f 00000030: 61 34 64 65 35 39 2c 66 6f 72 6d 61 74 3a 32 2c a4de59,format:2, 00000040: 76 65 72 73 69 6f 6e 3a 37 2c 66 6c 65 74 63 68 version:7,fletch 00000050: 65 72 3a 33 35 34 65 34 38 65 31 0a 00 00 00 00 er:354e48e1..... </pre> From the documentation: <blockquote> There are two file headers, which normally contain the exact same data. But once in a while, the file headers are updated, and writing could partially fail, which could corrupt a header. That's why there is a second header. Only the file headers are updated in this way (called "in-place update"). The headers contain the following data: </blockquote> <blockquote> The data is stored in one file. The file contains two file headers (for safety), and a number of chunks. The file headers are one block each; a block is 4096 bytes. </blockquote> The fields are broken down in version 1 of the docs as follows: * H: The entry "H:2" stands for the H2 database. * block: The block number where one of the newest chunks starts (but not necessarily the newest). * blockSize: The block size of the file; currently always hex 1000, which is decimal 4096, to match the * * disk sector length of modern hard disks. * chunk: The chunk id, which is normally the same value as the version; however, the chunk id might roll over to 0, while the version doesn't. * created: The number of milliseconds since 1970 when the file was created. * format: The file format number. Currently 1. * version: The version number of the chunk. * fletcher: The Fletcher-32 checksum of the header. === Additional files in H2's persistent implementation === H2's database objects are described as follows. It may be important to identify these together in a preservation context but the documentation is unclear as to whether the database file can be interpreted in its own right. {| ! File Name ! Description ! Number of Files |- | test.mv.db | Database file. Contains the transaction log, indexes, and data for all tables. Format: <database>.mv.db | 1 per database |- | test.newFile | Temporary file for database compaction. Contains the new MVStore file. Format: <database>.newFile | 0 or 1 per database |- | test.tempFile | Temporary file for database compaction. Contains the temporary MVStore file. Format: <database>.tempFile | 0 or 1 per database |- | test.lock.db | Database lock file. Automatically (re-)created while the database is in use. Format: <database>.lock.db | 1 per database (only if in use) |- | test.trace.db | Trace file (if the trace option is enabled). Contains trace information. Format: <database>.trace.db Renamed to<database>.trace.db.old if too big. | 0 or 1 per database |- | test.123.temp.db | Temporary file. Contains a temporary blob or a large result set. Format: <database>.<id>.temp.db | 1 per object |- |} == Use in digital preservation == Fedora 6.0's webapp is backed by a H2 database by default. == Further information == * [https://h2database.com/html/main.html H2 database documentation] * [https://github.com/fcrepo/fcrepo fcrepo] * [https://wiki.lyrasis.org/display/FEDORA6x/Properties fcrepo database configuration] * [https://github.com/h2database/h2database/issues/3892 GitHub issue asking for more information about format mapping] [[category:File formats with extension .db]] [[category:SQL]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/H2database H2database 2023-09-17T10:41:09Z

Ross-spencer: Initial summary information about H2 <hr /> <div>{{FormatInfo |subcat=Databases |extensions={{ext|db}} |mimetypes= |pronom= }} '''h2database''' (H2) is an open source JAVA SQL database that can be used as an embedded, server, or in-memory database. == Embedded format == H2's embedded format is a [https://www.h2database.com/html/mvstore.html#fileFormat MVStore file]. An example header is as follows: <pre> 00000000: 48 3a 32 2c 62 6c 6f 63 6b 3a 33 2c 62 6c 6f 63 H:2,block:3,bloc 00000010: 6b 53 69 7a 65 3a 31 30 30 30 2c 63 68 75 6e 6b kSize:1000,chunk 00000020: 3a 37 2c 63 72 65 61 74 65 64 3a 31 38 61 39 66 :7,created:18a9f 00000030: 61 34 64 65 35 39 2c 66 6f 72 6d 61 74 3a 32 2c a4de59,format:2, 00000040: 76 65 72 73 69 6f 6e 3a 37 2c 66 6c 65 74 63 68 version:7,fletch 00000050: 65 72 3a 33 35 34 65 34 38 65 31 0a 00 00 00 00 er:354e48e1..... </pre> From the documentation: <blockquote> There are two file headers, which normally contain the exact same data. But once in a while, the file headers are updated, and writing could partially fail, which could corrupt a header. That's why there is a second header. Only the file headers are updated in this way (called "in-place update"). The headers contain the following data: </blockquote> <blockquote> The data is stored in one file. The file contains two file headers (for safety), and a number of chunks. The file headers are one block each; a block is 4096 bytes. </blockquote> The fields are broken down in version 1 of the docs as follows: * H: The entry "H:2" stands for the H2 database. * block: The block number where one of the newest chunks starts (but not necessarily the newest). * blockSize: The block size of the file; currently always hex 1000, which is decimal 4096, to match the * * disk sector length of modern hard disks. * chunk: The chunk id, which is normally the same value as the version; however, the chunk id might roll over to 0, while the version doesn't. * created: The number of milliseconds since 1970 when the file was created. * format: The file format number. Currently 1. * version: The version number of the chunk. * fletcher: The Fletcher-32 checksum of the header. === Additional files in H2's persistent implementation === H2's database objects are described as follows. It may be important to identify these together in a preservation context but the documentation is unclear as to whether the database file can be interpreted in its own right. {| ! File Name ! Description ! Number of Files |- | test.mv.db | Database file. Contains the transaction log, indexes, and data for all tables. Format: <database>.mv.db | 1 per database |- | test.newFile | Temporary file for database compaction. Contains the new MVStore file. Format: <database>.newFile | 0 or 1 per database |- | test.tempFile | Temporary file for database compaction. Contains the temporary MVStore file. Format: <database>.tempFile | 0 or 1 per database |- | test.lock.db | Database lock file. Automatically (re-)created while the database is in use. Format: <database>.lock.db | 1 per database (only if in use) |- | test.trace.db | Trace file (if the trace option is enabled). Contains trace information. Format: <database>.trace.db Renamed to<database>.trace.db.old if too big. | 0 or 1 per database |- | test.123.temp.db | Temporary file. Contains a temporary blob or a large result set. Format: <database>.<id>.temp.db | 1 per object |- |} == Use in digital preservation == Fedora 6.0's webapp is backed by a H2 database by default. == Further information == * [https://h2database.com/html/main.html H2 database documentation] * [https://github.com/fcrepo/fcrepo fcrepo] * [https://wiki.lyrasis.org/display/FEDORA6x/Properties fcrepo database configuration] [[category:File formats with extension .db]] [[category:SQL]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Databases Databases 2023-09-17T10:09:31Z

Ross-spencer: /* Relational databases */ <hr /> <div>{{FormatInfo |formattype=electronic |thiscat=Databases |image=File manager.png }} See also [[Serialization]] for methods of storing, exporting, importing, and transferring structured data. Classes of databases: == CODASYL databases == * [[DBMS32]] (DEC) * [[DMS1100]] (Univac) * [[IDS/2]] (Honeywell) * [[IDMS]] (Cullinet, and later Computer Associates) == General databases == * [[BigTable]] (Google internal database) * [[DBF]] ** [[dBase II]] ** [[dBase III]] * [[LevelDB]] * [[Mork]] * [[PC-FILE]] * [[QDB (Robert R. Marsh)]] == Hierarchical databases == * [[IMS]] == ISAM (Indexed Sequential Access Method) == * [[Ability Database]] (.adb) * [[Access]] (was also known as Jet) * [[Extensible Storage Engine]] (ESE, EDB) * [[Paradox (database)]] == Multiformat platforms/programs/libraries/utilities == * [[Dat (data sharing)|Dat]] == NoSQL databases == * [[CouchDB]] * [[DynamoDB]] (AWS cloud database) * [[Elliptics]] * [[MongoDB]] * [[Clusterpoint]] == Object-oriented databases == * [[Cache]] * [[db40]] * [[Gemstone]] * [[Objectivity]] * [[ObjectStore]] * [[Versant]] == Relational databases == * [[Athena]] (AWS) * [[Cornerstone]] (Infocom) * [[Derby]] * [[FileMaker Pro]] * [[h2database]] * [[HSQLDB]] * [[IBM DB2]] * [[Ingres]] * [[MariaDB]] ** [[MariaDB error codes]] * [[MemSQL]] * [[MySQL]] ** [[MySQL error codesâ€Ž]] * [[Oracle]] ** [[ARC (database backup format)]] ** [[Oracle database error messages]] * [[PostGRESQL]] * [[SIARD]] * [[DB SQL Anywhere|SQL Anywhere]] * [[SQLite]] ** [[SQLite result codes]] * [[Virtuoso]] * [[DB (Watcom-SQL)|Watcom SQL]] == Triplestores == * [[3store]] * [[Apache Jena]] * [[Mulgara]] == XML databases == * [[BaseX]] * [[Documentum xDB]] * [[eXist-db]] * [[MarkLogic]] * [[Oracle XML DB]] * [[Qizx]] * [[Sedna]] * [[Tamino]] * [[TEXTML]] * [[TigerLogic XDMS]] * [[Xpriori XMS]] * [[XQuantum]] == Database programming/query languages == * [[Clipper (programming language)]] * [[dBase programming language]] * [[Fauna Query Language]] (FQL) * [[FoxPro programming language]] * [[SPARQL]] * [[SQL]] == Encrypted databases == * [[KBDX]] == Timeseries == * [[RRD]], round-robin database * [[Whisper]], used by graphite == Cloud/network/API databases == * [[FaunaDB]] * [[Wikibase]] (back end of Wikidata project from Wikimedia) == Uncategorized == * [[Apache Parquet]] * [[DeskMate Filer]] (.fil) * [[Folio Infobase]] (.nfo) * Info File [[FLR]] (.flr) * [[GNU Recutils]] [https://www.gnu.org/software/recutils/] * [[Microsoft Works Database]] * [[TDB (Samba)]] * [[Tabular Data Package]] == Conversion software == * [[Embulk]] == Links == * [http://blog.okfn.org/2013/04/24/frictionless-data-making-it-radically-easier-to-get-stuff-done-with-data/ Frictionless data] * [http://oddc.opendataresearch.org/ Open Data Research Network] * [http://www.chrisstucchio.com/blog/2013/hadoop_hatred.html Don't use Hadoop - your data isn't that big] * [http://readwrite.com/2013/10/28/why-proprietary-big-data-technologies-have-no-hope-of-competing-with-hadoop Why Proprietary Big Data Technologies Have No Hope Of Competing With Hadoop] * [http://www.itnews.com.au/News/357842,social-networks-stick-with-mysql.aspx Social networks stick with MySQL] * [http://scholarworks.umass.edu/cpo/vol1/iss1/4/ From Punched Cards to "Big Data": A Social History of Database Populism] * [http://support.microsoft.com/kb/168702 If you move your mouse continually the query may not fail. Do not stop moving] (that's Microsoft for you) * [http://boingboing.net/2014/01/31/whos-to-blame-for-daughter.html Who's to blame for 'Daughter Killed in Car Crash' mailing sent to parents? Big Data.] * [http://www.ft.com/cms/s/2/21a6e7d8-b479-11e3-a09a-00144feabdc0.html Big data: are we making a big mistake?] * [http://magazine.columbia.edu/features/winter-2013-14/ghost-files Big data analysis to see what's missing from the national archives] * [http://sbdevel.wordpress.com/2014/06/17/terabyte-index-search-and-faceting-with-solr/ Terabyte index, search and faceting with Solr] * [http://www.loc.gov/preservation/resources/rfs/data.html Library of Congress Recommended Format Specifications: Datasets] * [http://dataset.readthedocs.org/en/latest/ dataset: databases for lazy people (Python module)] * [http://www-01.ibm.com/software/data/infosphere/biginsights/resources.html IBM Hadoop info] * [http://www.database-preservation.com/ Database Preservation Toolkit] * [http://qntm.org/gay Gay marriage: the database engineering perspective]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/PDFXML PDFXML 2023-05-15T09:18:44Z

Ross-spencer: Additional links found while loking for the specification <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Page description languages |extensions={{ext|mars}}, {{ext|pdfxml}} |mimetypes={{mimetype|application/vnd.adobe.x-mars}}, {{mimetype|application/vnd.adobe.pdfxml}} |released=2006 }} Adobe labs developed a plugin for Acrobat to create an "XML-friendly representation of PDF".<ref>https://web.archive.org/web/20080919181131/https://blogs.adobe.com/mars/2008/09/pdfxml_plugin_prerelease.html</ref> Originally called the MARS project<ref>http://csis.pace.edu/~marchese/CS835/Student_Readings/p161-hardy.pdf</ref>, it was later renamed to PDFXML. Started in 2006, the project was shutdown in 2011 and removed from public access.<ref>https://web.archive.org/web/20110902063203/http://labs.adobe.com/technologies/mars</ref> == File Information == The PDFXML file format uses [[ZIP]] as a container format, and [[SVG]] for each page and [[JPEG2000]] for each image. File format specifications and schema were published at the time, but unfortunately the archive.org captures of the website have truncated PDF's.<ref>https://web.archive.org/web/20061222203316/http://labs.adobe.com/technologies/mars/</ref> If anyone has copies of the original specification or schema please post a link here. Basic container contains the following structure: <pre> â”œâ”€â”€ META-INF â”‚Â Â â”œâ”€â”€ compatibility.pdf â”‚Â Â â”œâ”€â”€ container.xml â”‚Â Â â””â”€â”€ metadata.xml â”œâ”€â”€ backbone.xml â”œâ”€â”€ bookmarks.xml â”œâ”€â”€ color â”‚Â Â â””â”€â”€ cs-0.icc â”œâ”€â”€ form â”‚Â Â â””â”€â”€ form_data.xfdf â”œâ”€â”€ mimetype â”œâ”€â”€ page â”‚Â Â â””â”€â”€ 0 â”‚Â Â â”œâ”€â”€ form_0.svg â”‚Â Â â”œâ”€â”€ form_1.svg â”‚Â Â â”œâ”€â”€ form_2.svg â”‚Â Â â”œâ”€â”€ info.xml â”‚Â Â â”œâ”€â”€ pg.can â”‚Â Â â””â”€â”€ pg.svg â””â”€â”€ script â”œâ”€â”€ javascripts.xml â””â”€â”€ js_0 </pre> ==Further information== Information not immediately visible through the references above. * [https://web.archive.org/web/20070824012806/http://labs.adobe.com:80/technologies/mars/faq.html MARS FAQ] * [https://web.archive.org/web/20070120074630/http://blogs.adobe.com/pdfdevjunkie/ MARS via PDF Junkie] * [https://zive.aktuality.sk/clanok/27631/projekt-adobe-mars-format-pdf-s-xml/ Martin KovÃ¡Ä on PDF XML] * [http://drmacros-xml-rants.blogspot.com/2006/12/adobe-mars-looks-interesting.html Eliot Kimber - Adobe Mars: Looks Interesting] * [https://microsoft.fandom.com/wiki/Portable_Document_Format#Mars Microsoft.Fandom: Adobe Mars] ==References== <references/> [[Category:Document]] [[Category:Adobe]] [[Category:ZIP based file formats]] [[Category:XML based file formats]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/U3D U3D 2023-04-12T14:04:38Z

Ross-spencer: Link to sample files <hr /> <div>{{FormatInfo |formattype=electronic |subcat=3D and CAD/CAM Models |extensions={{ext|u3d}} |released=2005 |pronom={{PRONOM|fmt/702}} |wikidata={{wikidata|Q974182}} }} '''U3D''' (Universal 3D) is a standardized format for storing compressed 3D graphical data. It was developed by a consortium of companies including Intel, Adobe, and Boeing, and issued as an ECMA standard (ECMA-363). It is supported for embedding in [[PDF]] files. == Identification == U3D files start with bytes {{magic|55 33 44}}, or "{{magic|U3D}}" in [[ASCII]]. == Specs == * [https://www.ecma-international.org/publications/standards/Ecma-363.htm ECMA standards index] ** [https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-363%201st%20edition.pdf 1st edition of standard] ** [https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-363%202nd%20Edition.pdf 2nd edition of standard] ** [https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-363%203rd%20edition.pdf 3rd edition of standard] ** [https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-363%204th%20Edition.pdf 4th edition of standard] == Sample files == * [https://github.com/ClinicalGraphics/u3d/tree/master/Samples/TestScenes github.com/ClinicalGraphics/u3d] sample files on GitHub. == Links == * [[Wikipedia:Universal 3D|Wikipedia article]] * [https://sourceforge.net/projects/u3d/ Sourceforge page] [[Category:Adobe]] [[Category:Hewlett-Packard]] [[Category:Intel]]</div>

Ross-spencer http://fileformats.archiveteam.org/wiki/Macintosh_resource_file Macintosh resource file 2023-03-08T13:25:41Z

Ross-spencer: Added links to some helper utilities and samples on GitHub <hr /> <div>{{FormatInfo |formattype=electronic |subcat=Resources |extensions={{ext|rsrc}}, {{ext|dfont}}, others }} The '''Macintosh resource file''' format was used by the Resource Manager in Mac OS Classic for storing resources used by Mac OS Classic applications as well as file associations and executable code. Traditionally, this format is used in the [[Resource Fork]] of a file on the [[HFS]] and [[HFS+]] file systems; however, when resource files are still used in Mac OS X applications, the same format is used in a file with the extension .rsrc. See [[Resource Fork]] for general information about Macintosh resource forks. == Format details == A resource has a [[FourCC|four-character type code]], an ID number, an optional name, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats. == Software == * [https://sourceforge.net/projects/rezilla/ Rezilla] * [https://github.com/kreativekorp/ksfl KSFL] reads and writes Macintosh resource files * {{Deark}} == Sample files == * https://telparia.com/fileFormatSamples/archive/rsrc/ == References == * [[Wikipedia:Resource fork|Resource fork (Wikipedia)]] * [http://developer.apple.com/legacy/mac/library/documentation/mac/pdf/MoreMacintoshToolbox.pdf More Macintosh Toolbox] (format is described on page 1-121 to 1-125) * [https://github.com/kreativekorp/ksfl/wiki/Macintosh-Resource-File-Format Description of the file format] from the KSFL wiki * [https://whitefiles.org/mac/pgs/t02.htm The White Files: Mac OS Guides: Resources] * [http://xahlee.info/UnixResource_dir/macosx.html Mac OS X Resource Fork and Command Line Tips] == See also == * Kaitai structs for a few resource fork files on [Macintosh resource file GitHub]. * Official Kaitai [https://github.com/kaitai-io/kaitai_struct_formats/tree/master/macos MacOS Structs]. * RSRC dump [https://github.com/dgelessus/python-rsrcfork pure Python utility for reading resource data]. * Resource-fork hashtag [https://github.com/topics/resource-fork on Github]. [[Category:Metadata]] [[Category:Development]] [[Category:Macintosh]]</div>

Ross-spencer
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:97) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38