## TrustedQSL High Level Virtual Record Design Notes

by
Michael Keane K1MK
k1mk@alum.mit.edu

1. Built-In (or Spec Defined) Signed Field
   - The name of this field is included in a TBD list of field names defined in the Gabbi specification.
   - Value of this field is incorporated into "virtual record" used for calculating digital signature
   - External representations of the value of this field shall be encoded using a TBD set of formatting rules given in the Gabbi
   - The formatting rules must result in an unambiguous bi-directionalmapping between a data value and its unique external represestation.
   - Database design must save the value of this field.
   - Database design may employ internal representations for storing the value of the field that differ from the external representation. E.g., numeric values maye be stored as a binary number rather than as a string of digit characters.
   - Only ASCII characters shall be used in field name and in the external representation of the value of this field [TBR]

2. Built-In (or Spec Defined) Unsigned Field
   - The name of this field is included in a TBD list of field names defined in the Gabbi specification.
   - Field name shall also employ a TBD mechanism designating this as an "unsigned" field
   - Value of field is ommitted from the "virtual record" used for calculating digital signature
   - Database design may decline to save this field
   - Only ASCII characters shall be used in field name
   - Any valid Unicode characters may be used in the field value [TBR]

3. User Defined Signed Field
   - Field name is not in the union of the lists of signed and unsigned fields defined in the Gabbi spec
   - Value of field incorporated into "virtual record" for calculating digital signature
   - Database design must save the unprocessed octet strings representing this field's name and its value. These strings shall be saved in the functional equivalent of a table
   - Any valid Unicode characters may be used in the field name and field value [TBR]

4. User Defined Unsigned Field
   - Field name is not in the union of the lists of signed and unsigned fields defined in the Gabbi specification
   - Field name shall also employ a TBD mechanism designating this as an "unsigned" field
   - Value of field is ommitted from the "virtual record" used for calculating digital signature
   - Database design may decline to save this field
   - Any valid Unicode characters may be used in the field name and field value [TBR]