The British National Archives has registered SQLite3 among its
identified file formats (see PRONOM at
http://www.nationalarchives.gov.uk/pronom/Default.aspx) and given it the
following PUID: fmt/729.
The U.S. Library of Congress has included SQLite3 in its Recommended
Formats Statement for the digital preservation of datasets
(http://www.loc.gov/preservation/resources/rfs/data.html).
Hope this helps.
Am 08.07.2016 um 04:17 schrieb Richard Hipp:
On 7/7/16, Henry Chan <[email protected]> wrote:
Dear all,
I'm wondering if there is any "formal" specification for the sqlite3
application format, as in standardized as an ISO/IEC standard, ECMA
standard or RFC?
How does one go about getting a long-established file format such as
SQLite "formalized"?
This is similar to .DOCX being registered as both ISO/IEC 29500
and ECMA-376; JSON being RFC 7159 and ECMA-404, XML being a W3C
specification with various parts as RFC.
Without a "formal" specification, it makes it (unnecessarily) "hard" for
governments to adopt SQLite3's database file as an application format as an
official formats for information exchange.
Such a "formal" specification would simply be a stripped down version of
Section 1 of http://www.sqlite.org/fileformat2.html, where all the reasons
for quirks or definite behavior are stripped and all values could be
described in the database' committed state.
Yours,
Henry
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
