Naming ProposalLink to the section Naming Proposal
On this page
Status: Decided 2026-10-14. The project sponsor selected UNIVIP — Universal Vehicle Interoperability Protocol (section 2d) and purchased univip.org (domain owned since 2026-10-14). The repository was renamed from the working name ODIP in the same change (schema identifiers univip.*, URNs urn:univip:, paths /univip/v1, scopes univip.*, DNS-SD _univip._tcp). Trademark registration in classes 9 and 42 is the next step. The sections below are kept as the record of how the name was chosen. No trademark search has been completed yet.
1. What a good name must doLink to the section 1. What a good name must do
- Work on a datasheet next to "ONVIF": "<Name> Profile S conformant".
- Be pronounceable in one way, in most languages, and spellable after hearing it once.
- Not collide with a well-known product, standard or protocol in security, aviation or software.
- Not depend on the word "drone" so the standard can cover docks, tethered aircraft, robots and future autonomous platforms.
- Have a plausible
.orgdomain and a defensible trademark position (coined or arbitrary words are strongest; descriptive acronyms are weakest).
2. ShortlistLink to the section 2. Shortlist
| Name | Expansion / idea | Strengths | Risks to check |
|---|---|---|---|
| Kestrel | A small falcon that hovers in place while watching the ground: literally a hovering observer. Tagline: "Kestrel: the open standard for drone video and control interoperability." | Memorable, brandable, no acronym to explain, works as a word ("Kestrel conformant"), evokes exactly the use case | Common bird name used by unrelated products (weather meters, software tools); kestrel.org likely taken, so kestrelstandard.org or kestrel-interop.org; V-22 Osprey shows aviation bird names can be trademarked |
| AVIP | Aerial Video Interoperability Profile(s) | Sounds like a standard, sits naturally next to ONVIF, descriptive enough to self-explain | Four-letter acronyms are weak trademarks; "Profile" in the name clashes slightly with having Profiles S/C/N inside it (could be "Aerial Video Interoperability Protocol") |
| SkyFrame | Frame-synchronized video and telemetry from the sky | Descriptive of the core technical idea (every frame carries its geospatial context), brandable | Compound-word marks are often already in use for software; check |
| OpenAerial | Open Aerial Interoperability | Signals "open" and the domain in two words; consistent with OpenAPI, OpenTelemetry naming | Generic; harder to trademark; openaerial.org may be taken |
| UVIS | Unmanned Video Interoperability Standard | Pronounceable ("you-vis"), descriptive | Dull; "unmanned" is being phased out in favor of "uncrewed" in regulatory language |
| ODIP (current) | Open Drone Interoperability Protocol | Already in use here; descriptive | "Drone" narrows scope; acronym is forgettable; unknown collisions |
Names considered and rejected: ODIN (heavily trademarked in software), Osprey (Bell Boeing aircraft), Argus (multiple camera and surveillance products), Aeris (IoT telecom company), OpenSky (ADS-B network), Open Drone ID (existing Remote ID project), OpenFlight (existing 3D format), DroneLink (existing product), OVID (unfortunate phonetic proximity to COVID), AVIS (car rental), Wing (Alphabet's drone company).
2b. Cross-domain acronyms (requested 2026-10-14)Link to the section 2b. Cross-domain acronyms (requested 2026-10-14)
The sponsor asked for a short acronym-style name in the spirit of "Aerial Interoperability Protocol" that also covers uncrewed underwater vehicles (UUVs, ROVs) and, by extension, surface and ground vehicles. "Aerial" therefore has to go. Candidates, in order of preference:
| Acronym | Expansion | Said as | Covers | Notes and risks to check |
|---|---|---|---|---|
| UVIP | Unmanned (or Uncrewed) Vehicle Interoperability Protocol | "you-vip" | UAV, UUV, USV, UGV | The "U" reads as either Unmanned (industry) or Uncrewed (regulators), so the expansion can change without changing the name. Pattern matches ONVIF. Check uvip.org, class 9/42 marks. |
| UxVIP | UxV Interoperability Protocol (UxV = defense shorthand for UAV/UUV/USV/UGV) | "you-ex-vip" | all domains | Precise for defense and maritime audiences; the lowercase x hurts datasheets and domains (uxvip.org). |
| UVIS | Unmanned/Uncrewed Vehicle Interoperability Standard | "you-vis" | all domains | "Standard" is honest only after conformance exists; "Protocol" is safer early. |
| RVIP | Remote Vehicle Interoperability Protocol | "ar-vip" | ROVs, RPAS, remote ground | "Remote" matches ROV and RPAS terminology; weaker for autonomous vehicles. |
| MSIP | Mobile Sensor Interoperability Protocol | "em-sip" | any moving sensor platform | Domain-neutral and VMS-friendly ("a drone is a mobile sensor"); does not say "vehicle", which may suit robotics but reads vaguer. Check collisions (MSIP is used in finance). |
| OVIP | Open Vehicle Interoperability Protocol | "oh-vip" | all | "Vehicle" alone suggests cars; weaker. |
Rejected for this round: ONVIP and UVIF (too close to ONVIF, confusion and trademark risk), AVIP/AIP (aerial only), DIP (collides with many uses).
Recommendation for this round: UVIP, fallback UVIS. Both keep the ONVIF-style cadence, both survive the "unmanned" to "uncrewed" terminology shift, and both are honest about covering air and water. If UVIP is chosen, the command family becomes vehicle.* per ADR-0007.
2c. Five-letter acronyms ending in VIP (requested 2026-10-14)Link to the section 2c. Five-letter acronyms ending in VIP (requested 2026-10-14)
Sponsor constraint: five letters, ending in VIP = Vehicle Interoperability Protocol, domain-neutral (air and underwater at least).
| Acronym | Expansion | Said as | Why it works | Risks to check |
|---|---|---|---|---|
| NAVIP | Networked Autonomous Vehicle Interoperability Protocol | "nav-ip" | Reads as "navigation IP"; easiest to say and remember; "networked" signals the VMS/C2 integration purpose | "Autonomous" under-sells remote-piloted vehicles; check navip.org and existing NAVIP marks |
| MOVIP | Multi-domain Open Vehicle Interoperability Protocol (alt. Mobile Observation Vehicle IP) | "moh-vip" | "Multi-domain" states the air/sea/land scope outright; "Open" signals the licence; smooth to say | Generic-sounding; check collisions |
| OUVIP | Open Uncrewed (Unmanned) Vehicle Interoperability Protocol | "oo-vip" | Most literal; keeps "Open" and the U that survives the unmanned → uncrewed shift | Slightly awkward to pronounce; two vowels up front |
| UXVIP | UxV Interoperability Protocol (UxV = UAV/UUV/USV/UGV) | "you-ex-vip" | Precise for defence and maritime readers; explicitly all domains | Jargon outside defence; the x breaks the "it is a word" feel |
| ROVIP | Remotely Operated Vehicle Interoperability Protocol | "roh-vip" | Natural for underwater (ROV is the standard term) and for RPAS; very pronounceable | Reads underwater-first to aviation people; excludes fully autonomous vehicles by name |
| ASVIP | Air–Sea Vehicle Interoperability Protocol | "as-vip" | Names both target domains explicitly | Excludes ground vehicles by name; weaker brand |
| AUVIP | Autonomous Uncrewed Vehicle Interoperability Protocol | "aw-vip" | Smooth; "AUV" is a well-known underwater term | Reads as underwater-only (AUV = autonomous underwater vehicle) |
| OMVIP | Open Mobile Vehicle Interoperability Protocol | "om-vip" | Simple | "Mobile vehicle" is redundant; bland |
| Open Network Vehicle Interoperability Protocol | "on-vip" | Deliberately echoes ONVIF | Not recommended: one letter from ONVIF invites confusion and a trademark objection from the body we want as a partner |
Recommendation: NAVIP first, MOVIP second, OUVIP third. All three are domain-neutral and keep the ONVIF cadence. NAVIP is the most memorable and self-explaining; MOVIP states the multi-domain scope most honestly; OUVIP is the most literal. Trademark and domain checks decide between them.
2d. Five-letter names built from "Networked Interoperability Protocol for Autonomous Vehicles" (requested 2026-10-14)Link to the section 2d. Five-letter names built from "Networked Interoperability Protocol for Autonomous Vehicles" (requested 2026-10-14)
Sponsor preference: the phrase Networked Interoperability Protocol for Autonomous Vehicles; five letters; no requirement to end in VIP.
| Name | Expansion | Said as | Why it works | Risks to check |
|---|---|---|---|---|
| ANVIL | Autonomous Networked Vehicle Interoperability Layer | "anvil" | A real word: memorable, strong, easy in every language; "layer" is accurate (the standard is an interoperability layer over native protocols) | Common word with many software marks; a trademark in class 9/42 may be contestable; anvil.org certainly taken, so anvilprotocol.org or anvil-interop.org |
| ONAVI | Open Networked Autonomous Vehicle Interoperability | "oh-navi" | "Navi" evokes navigation; "Open" up front; smooth to say; coined so it is trademarkable | Check against Onavo (former Meta VPN, defunct) and Navi marks |
| NAVOP | Networked Autonomous Vehicle Open Protocol | "nav-op" | Keeps the sponsor's words plus "Open"; crisp | Check collisions; "op" may read as "operations" |
| IPNAV | Interoperability Protocol for Networked Autonomous Vehicles | "ip-nav" | Nearly the sponsor's exact phrase; reads as "IP navigation" | May be mistaken for a networking or GNSS product |
| ANVIP | Autonomous Networked Vehicle Interoperability Protocol | "an-vip" | Exact words, exact meaning | Less distinctive than ANVIL; VIP ending |
| NEXAV | Networked EXchange for Autonomous Vehicles | "nex-av" | Coined, modern, trademarkable | "Exchange" is looser than "protocol"; check marks |
| NAVIX | Networked Autonomous Vehicle Interoperability eXchange | "nav-ix" | Coined, short | Existing Navix marks in other sectors; check |
| AVIOP | Autonomous Vehicle Interoperability Open Protocol | "av-ee-op" | Literal | Harder to say |
| Networked Interoperability Protocol for Autonomous Vehicles | "nip-av" | The sponsor's exact word order | Avoid: the first syllable is an ethnic slur in English | |
| Networked Autonomous Vehicle Interoperability Standard | "nav-iss" | Latin for ship | Avoid: Navis is a major maritime terminal-software brand, a direct collision in our underwater/maritime scope | |
| — | — | — | Avoid: India's satellite navigation system (NavIC) | |
| Open Protocol for Networked Autonomous Vehicles | "op-nav" | Good words | Avoid: OPNAV is the US Navy's Office of the Chief of Naval Operations | |
| — | — | — | Avoid: Emlid Navio autopilot hardware, a direct drone-market collision |
Recommendation for this round: ANVIL (brandable) or ONAVI (coined, safest to trademark), with NAVOP as the literal fallback. If "Protocol" must appear in the expansion, ONAVI can be read as Open Networked Autonomous Vehicle Interoperability (Protocol) on the website while the five letters stay as the brand.
2d. Six-letter names, no structural restriction (requested 2026-10-14)Link to the section 2d. Six-letter names, no structural restriction (requested 2026-10-14)
Sponsor feedback: Networked Autonomous Vehicle Interoperability Protocol captures the meaning; anvil.org is taken. Six-letter candidates whose meaning still matches (networked, uncrewed/autonomous, air + water, interoperability):
| Name | Said as | Meaning / expansion | Why it fits | Risks to check |
|---|---|---|---|---|
| UNIVIP | "you-ni-vip" | Universal Vehicle Interoperability Protocol | "Universal" says every domain (air, sea, land) in one word; keeps the VIP ending already chosen; acronym reads as a word | univip.org; existing marks |
| GANNET | "gan-net" | Seabird that flies and dives deep underwater | The only animal that literally operates in both target domains; brandable like Kestrel; "net" inside the word hints at networked | Gannett (media company, double-t) phonetic collision; gannet.org |
| UNVEIL | "un-veil" | Uncrewed Networked Vehicle Exchange & Interoperability Layer | Real word meaning "reveal / bring into view", which is what the protocol does for a VMS; strong backronym | Common English word, weaker trademark; unveil.org |
| OPENVI | "open-vee-eye" | Open Vehicle Interoperability | Sits with OpenAPI, OpenTelemetry, OpenID naming; states openness and scope plainly | Descriptive, harder to defend; openvi.org |
| AERSUB | "air-sub" | aer (air) + sub (subsea) | Coined word naming exactly the two domains requested; strong trademark position | Excludes ground vehicles by name; needs explaining once |
| NAVIOP | "nav-ee-op" | Networked Autonomous Vehicle Interoperability Open Protocol | Direct six-letter extension of NAVIP keeping the full meaning the sponsor liked | Less fluent than NAVIP |
| TRIDOM | "try-dom" | Tri-domain (air, sea, land) | States multi-domain scope; coined | Does not say "vehicle" or "interoperability" without the tagline |
| UXVNET | "you-ex-vee-net" | UxV Network | Precise for defence/maritime readers; "net" = networked | Jargon; hard to say |
| AVLINK | "ay-vee-link" | Autonomous Vehicle Link | Simple and clear | "AV" collides with audio-visual; likely existing marks |
| NAVIGO | "nav-ee-go" | Latin-derived "I navigate", from navis (ship) | Covers sea and air by etymology | Paris transit card of the same name; collision |
Recommendation: UNIVIP for an acronym, GANNET for a brand word. UNIVIP keeps everything the sponsor liked about NAVIP (meaning, VIP ending, ONVIF cadence) and replaces "networked autonomous" with "universal", which covers more vehicles in fewer letters. GANNET is the strongest brandable option if a word rather than an acronym is preferred: a bird that both flies and dives is the exact metaphor for an air-and-underwater standard. Trademark and domain checks decide.
3. Recommendation (original, aerial-scoped round)Link to the section 3. Recommendation (original, aerial-scoped round)
Primary: Kestrel. It is the only candidate that is simultaneously memorable, meaningful, scope-neutral and brandable. The standard would be "Kestrel", the profiles "Kestrel Profile S/C/N", the schema prefix kestrel.telemetry.v0.1, the discovery service _kestrel._tcp, the scopes kestrel.view etc.
Fallback if Kestrel fails the trademark or domain check: AVIP, expanded as Aerial Video Interoperability Protocol, which reads as a sibling of ONVIF and self-explains on a datasheet.
4. Checks to run before decidingLink to the section 4. Checks to run before deciding
- Trademark search in classes 9 (software, apparatus) and 42 (software services) in the US, EU, UK, India and China, for the exact word and close phonetic variants.
- Domain availability:
<name>.orgpreferred;<name>standard.org,<name>-interop.orgacceptable. - GitHub organization name availability.
- Search of existing standards registries (ISO, IEC, IEEE, ONVIF, OASIS, OGC, MISB, ASTM) for the name.
- Pronunciation check with non-native English speakers.
5. Rename procedure (when decided)Link to the section 5. Rename procedure (when decided)
- ADR recording the decision and the chosen expansions.
- Single commit replacing
odip/ODIPtokens inschemas/($id,schemaconstants),examples/,api/,spec/,docs/,tools/, and the repository name. - Run
tools/validate.py. - Tag
0.1.0-draftunder the new name; the old name is kept inCHANGELOG.mdfor history.