search

iftechfoundation / ifarchive-if-specs

Specification documents for the Glk, Glulx, and Blorb standards
15 stars 4 forks source link

Should Babel have general support for UUID://...// convention? #4

Open erkyrath opened 2 years ago

erkyrath commented 2 years ago

This is the idea that, if all else fails, you should scan the file for the literal text "UUID://...//". Several existing formats work this way (Z-code, Glulx, Alan, HTML as a fallback) but it's never discussed as a general rule.

If we adopted it as a general rule, then new IF formats could provide IFID information to babel without having to go through a formal process of updating the spec and the babel source.

Secondary question: all files, or just files that babel doesn't recognize? In other words, should we add this as a fallback for Hugo, Adrift, TADS, etc? I don't expect this case would ever arise in real life, but it would make the implementation simpler.

curiousdannii commented 2 years ago

Perhaps also ifid:...? possibly with a space after the colon.