Discussion on Profile Structure Point46

From wiki.gpii
Jump to: navigation, search


  • Multiple properties, one for each unit
  • Compound values, e.g. [number:12, unit:pt]
  • Define multiple encoding schemas for the values that can be clearly distinguished
  • Code units as part of conditions
  • Commit to one normalized unit as part of the specification for a COMMON property, and convert other units


  • Normalized values are good for easy matchmaking
  • Matchmaker will have to convert to normalized unit anyway
  • The user's preferences determine in what unit to display to the user
  • There are application-specific units which could be stored as part of an application-specific property value

Tentative decision: Use normalized units, and use application-specific properties if other units need to be stored in the profile.