Paul P
So we have a programming language that has no official specification
Like MIDI it does have a specification (SFZ 2.0), but is not an official
standard - companies can modify it if they want. Unfortunately I am not aware of any standards committee that has the SFZ spec on its docket. Remember, back in the dawn of time itself, when dinosaurs ruled the earth, SFZ was intended simply as a better option than Sound Fonts and DLS when moving audio files and mappings from one environment to another. The extra opcodes are a bonus.
According to Patch Arena, Plogue's Sforzando handles all Dim Pro supported opcodes. If you design something for Dim Pro, it should work in Sforzando. Camel Audio's Alchemy and Alchemy Player recognize the 'region' and 'group' headers and various opcodes (sample, pitch_keycenter, lokey, hikey, key, lovel, hivel, loop_mode, cutoff, fil_veltrack, default_path, volume, tune, pan, seq_position, trigger, sw_last).
Those are the main needed upcodes anyway. If you design for that minimum set, your file will play back as expected in the common SFZ players (assuming the file paths are correct).
For those reading this who are curious about SFZ files, here's a link to
an article I wrote in Keyboard magazine that covers the basics.