That's a good point. It therefore might be useful if they were better at communicating that what they are doing is not just a dichotomy of identified or not, where unidentified could be anything, and instead they are using a range that includes exactly identified (it was flight UA 376), characterized (it was a distant plane made to look like a triangle by bokeh) and isolated (we have this video showing green triangles, not yet sure what it might be.) Now, if they say "We have 400 reports, 50 are identified" the public impression is that they 350 possible flying saucers, whereas saying "We have 400 reports, 50 identified, 300 characterized to the level of planes/balloons/etc." there is at least a more accurate sense of the scale of the possible number of cases that could be something previously unknown, without giving away anything in terms of procedures or capabillities.
Would it be possibly helpful in drawing that distinction more clearly, and in helping folks to understand that there is an intermediate step where they/we know it was a bird, but don't know if it was a duck or an albatross, if MB adopted that same terminology and scale of "identifiedness?"
The terminological confusion boils down to the term "identify" being commonly employed in two very different contexts when discussing the UAP:
(1) The context of mitigating or eliminating a security risk (military, law enforcement, security services, surveillance, intelligence); in this context "identify" has a very specific meaning, referring to the process of determining with reasonable confidence the nature, the level of hostility and the target of each individual object as well as the potential damage caused by it.
(2) The context of explaining a phenomenon (science, news reporting, academic or amateur knowledge pursuits);
Within context 1 the purpose of "identifying" a UAP is to describe a specific object in terms of the threat it poses. Within context 2 the purpose of "identifying" a UAP is to explain the phenomenon -- a task which may or may not require as many details, or the same details, about the object than context 1. In other words, depending on the context, a different (whilst related) question is asked about the UAP that calls for a resolution (an identification).
An object may be satisfactorily "identified" within context 2 (a plane, a drone) while remaining "unidentified" within context 1 (which exact plane? which exact drone?). An object may even be "unidentified" in both contexts while resolving the specific question of extraordinary flight patterns. Several possible and known phenomena may explain unusual flight patterns (i.e. 'unusual' at a cursory glance) which can be satisfactorily demonstrated not to be physics-defying, and thereby effectively demystifying the UAP. In other words, a UAP can be satisfactorily explained as non-extraordinary without the need to identify it in either context.
In order to perform a satisfactory "identification" under context 1 (especially in the military), the exact type, role, configuration and origin of the sighted capability are important details coupled with its flight path and overall behaviour in a threatening or non-threatening manner. For example:
Type: McDonnell Douglas F-15E
Configuration: Weapons-carrying with 4 Sidewinders, 2 AMRAAMs, and x, y and z air-to-ground weapons
Origin: Country X
Flight Path and Behaviour: On a descent at location p, weapons z and y hot, towards a column of 8 main battle tanks at location q.
This level of detail is obviously a tall order to satisfy with fuzzy splotches and whizzing pixels which, without supporting data, are doomed to remain "unidentified". On the other hand, sometimes an object may be justifiably deemed a threat even when it's not properly identified (but perhaps vaguely "characterized") whilst spotted during an active military engagement and demonstrating threatening behaviours within the proximity of critical targets.
"Identifying" a phenomenon in the 2nd context of "explaining" it is essentially a category mistake where a security risk assessment term is flippantly adopted and bandied about in a journalistic or scientific context. As has been pointed out earlier on this thread, it is perfectly possible to reach reasonable confidence on the generic type and character of a phenomenon (a bird, a plane, a plastic bag, a drone) without exactly "identifying" the individual object in terms of its specifics (model, make, unit, mileage, species, subspecies, age, life cycle phase, gender, product number, barcode, you pick your particular).
For improved communication with the general public it would make sense for defence spokespersons to clarify this terminological confusion by stating something to the following effect:
"Unidentified", in the military context, does not mean the military does not have a likely non-alien explanation for a given UAP. Neither does our limited public disclosure of these likely explanations imply their absence. In many cases it just means we lack a number of specific details required to complete a by-the-book threat-identification.