Based on this:

http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions

" 
.ogg - audio/ogg

    * Ogg Vorbis I Profile
    * .ogg applies now for Vorbis I files only
    * .ogg has more recently also been used for Ogg FLAC and for Theora, too — these uses are deprecated now in favor of .oga and .ogv respectively
    * has been defined in RFC 3534 http://www.ietf.org/rfc/rfc3534.txt for application/ogg, so rfc 3534 will be re-defined 

RATIONALE: .ogg has traditionally been used for Vorbis I files, in particular in HW players, hence it is kept for backwards-compatibility 
"

Seems like audio/ogg and application/ogg are both correct.

Thanks for your input Urho!

> Seems like audio/ogg and application/ogg are both correct.

  Yeah! seems so but not "audio/ogg+vorbis" which is what tracker is reporting, unless i missed something in that document you referred to?

Nope, I'm not saying that all is well. Just reported that those two should be ok. 

Changing the Product to "glib" since the results can be reproduced with the following GIO example code:

<ValaCode>
        File file = File.new_for_uri (uri);

        weak FileInfo file_info;

        try {
            file_info = file.query_info (FILE_ATTRIBUTE_STANDARD_CONTENT_TYPE,
                                         FileQueryInfoFlags.NONE,
                                         null);
        } catch (Error error) {
           ...
        }

        weak string content_type = file_info.get_content_type ();
        weak string mime = g_content_type_get_mime_type (content_type);
</ValaCode>

  Where 'uri' is a URI to an ogg vorbis file.

This bug needs to be reported against the shared-mime-info product in bugs.freedesktop.org