A short note by Ralph Griswold explaining how profile drafts can be stored in WIF (Weaving Information File) files even though the format has no provision for them. The trick is to name blocks with numbers instead of letters, treating blocks as shafts and treadles, and entering the profile as a threading draft. It also suggests flagging such a WIF in the [INFO] section, in the file name, or in external documentation, and notes that any threading draft can serve as a profile draft.