System Use Sharing Protocol

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
m (Format details)
 
(2 intermediate revisions by one user not shown)
Line 7: Line 7:
  
 
== Format details ==
 
== Format details ==
Each ISO 9660 member file has an optional "system use area", whose use is undefined by the ISO 9660 standard. SUSP divides this area into tagged "entries", and defines some standard entry types. Other standards built on SUSP, notably [[Rock Ridge]], define additional entry types. The [[Wikipedia:Rock Ridge|Wikipedia article for Rock Ridge]] has a list of entry tags.
+
Each ISO 9660 member file has an optional "system use area", whose use is undefined by the ISO 9660 standard. SUSP divides this area into tagged "entries", and defines some standard entry types. Other standards built on SUSP, notably [[Rock Ridge]], define additional entry types.
  
 
Technically, non-core entries are namespaced, using the extension ID string in one or more "ER" entries. Known ID strings:
 
Technically, non-core entries are namespaced, using the extension ID string in one or more "ER" entries. Known ID strings:
* "<code>RRIP 1991A</code>" = [[Rock Ridge]] 1.10
+
* "<code>RRIP 1991A</code>" = [[Rock Ridge]] 1.09, 1.10
* "<code>IEEE_P1282</code>" = [[Rock Ridge]] 1.12
+
* "<code>IEEE_P1282</code>" = Rock Ridge 1.12
 +
* "<code>IEEE_1282</code>" = Arguably a valid Rock Ridge ID
 +
* "<code>AAIP_0100</code>", "<code>AAIP_0200</code>" = [[AAIP]]
 +
 
 +
Some extensions (e.g. [[zisofs]]) that maybe ought to be SUSP lack their own "ER" ID, and instead are essentially rogue extensions of [[Rock Ridge]].
 +
 
 +
Refer to [[ISO 9660#Extensions]] for a list of extensions, some of which are extensions of SUSP and/or Rock Ridge.
 +
 
 +
The [[Wikipedia:Rock Ridge|Wikipedia article for Rock Ridge]] also has a list of entry tags.
  
 
== Identification ==
 
== Identification ==
Line 19: Line 27:
 
* [ftp://ftp.ymi.com/pub/rockridge/susp112.ps SUSP draft standard v1.12]
 
* [ftp://ftp.ymi.com/pub/rockridge/susp112.ps SUSP draft standard v1.12]
 
* [http://cdrtools.sourceforge.net/private/RRIP/susp.ps SUSP draft standard v1, rev. 1.10]
 
* [http://cdrtools.sourceforge.net/private/RRIP/susp.ps SUSP draft standard v1, rev. 1.10]
 +
* {{CdTextfilesURL|internetinfo/standards/iso/9660/rockridge/}} ... - Proposal v1 rev. 1.09
  
 
[[Category:Metadata]]
 
[[Category:Metadata]]

Latest revision as of 19:31, 5 February 2019

File Format
Name System Use Sharing Protocol
Ontology
Released ~1991

System Use Sharing Protocol (SUSP) is a standard that specifies a uniform way to extend ISO 9660 (CD-ROM) format, to attach arbitrary metadata to each file. It is standardized as IEEE P1281.

[edit] Format details

Each ISO 9660 member file has an optional "system use area", whose use is undefined by the ISO 9660 standard. SUSP divides this area into tagged "entries", and defines some standard entry types. Other standards built on SUSP, notably Rock Ridge, define additional entry types.

Technically, non-core entries are namespaced, using the extension ID string in one or more "ER" entries. Known ID strings:

  • "RRIP 1991A" = Rock Ridge 1.09, 1.10
  • "IEEE_P1282" = Rock Ridge 1.12
  • "IEEE_1282" = Arguably a valid Rock Ridge ID
  • "AAIP_0100", "AAIP_0200" = AAIP

Some extensions (e.g. zisofs) that maybe ought to be SUSP lack their own "ER" ID, and instead are essentially rogue extensions of Rock Ridge.

Refer to ISO 9660#Extensions for a list of extensions, some of which are extensions of SUSP and/or Rock Ridge.

The Wikipedia article for Rock Ridge also has a list of entry tags.

[edit] Identification

The known versions of SUSP include the byte sequence 53 50 07 01 be ef. In most cases, this sequence will appear at offset 2048×{the 32-bit little-endian int at offset 32926} + 34.

[edit] Specifications

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox