Vendor namespace addition

[vrunkel]

Please add EO as vendor namespace for ecoObs. We are adding GUANO support to the next version of ecoBatRec, our iOS application. We also add GUANO support to our software bcAdmin when exporting wave files from the database.

Volker Runkel, developer and managing director at ecoObs GmbH

[riggsd]

Greetings Volker, I strongly urge you to use the more descriptive namespace ecoObs rather than the cryptic prefix EO. Is this possible?

[vrunkel]

Hello David, ecoObs it will be then, no problem. The EO stems from the current short notations of other vendors, but is not a necessity for us. thx!

…

Am 07.07.2026 um 14:54 schrieb David A. Riggs ***@***.***>: riggsd left a comment (riggsd/guano-spec#12) <#12 (comment)> Greetings Volker, I strongly urge you to use the more descriptive namespace ecoObs rather than the cryptic prefix EO. Is this possible? — Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=AC4YKN5TK2BTMGTIZIDT4VL5DTXHJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJQGQYDANRTGE32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4904006317>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC4YKN5FFTR34QO4THYOWJL5DTXHJAVCNFSNUABEKJSXA33TNF2G64TZHM4DMMJZGQ3DKOJ3JFZXG5LFHM2DQMRVG43TQNJXHCQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AC4YKN2FLPQYWYMGBFR4PT35DTXHJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJQGQYDANRTGE32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AC4YKNYATML6ROAOD7AYPNT5DTXHJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJQGQYDANRTGE32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.

[riggsd]

Excellent, I'll add the ecoObs namespace to the list. Feel free to pass on a URL if you choose to publicly document your namespaced metadata fields.

I regret that some of the early vendors used very terse namespaces, but am pleased for widespread adoption and interoperability.

Thanks very much!