[media-types] [IANA #1452734] image/prs.aimg registrat ion request

Hi Darrel,

We received a follow-up message from the applicant for image/prs.aimg audio/prs.aaud, and video/prs.avid:

===

UPDATE:

To IANA Media Types Review Team,

I would like to amend my registration requests (tickets #1452734, #1452733, #1452731) for the following media types:

image/prs.aimg
audio/prs.aaud
video/prs.avid

Request 1 – Change contact information in all three registrations from: Elvis Ouma to Ai Media Format.

(Please remove my alias name from all records.)

The email address remains: [email protected]

Request 2 – Move from Private Use to Standard Tree

Please move all three media types from the prs (Personal/Private) tree to unprefixed standard media types as follows:

Current	Requested
image/prs.aimg	image/aimg
audio/prs.aaud	audio/aaud
video/prs.avid	video/avid
Reason for this request:

The actual file extension being deployed is .aimg, .aaud, and .avid — not .prs.aimg, .prs.aaud, or .prs.avid.

Registering as image/prs.aimg would create a direct mismatch between the registered MIME type and the actual file naming convention used in production. This would cause:

Interoperability issues across browsers, CDNs, and media servers that rely on MIME type detection

Confusion for developers implementing the format

A need to rename all existing files or break backward compatibility in the future

The implementation is complete, the specification is published, and the format is ready for deployment. Registering as standard types from the beginning ensures that the MIME type matches the file extension exactly, avoiding unnecessary complexity and technical debt.

Request 3 – Update Published Specification URL

Please update the "Published specification" field from:

https://github.com/ai-mf/media-engine/blob/main/spec/ai-media-format.md

to:

https://github.com/aimediaformat/media-engine/blob/main/spec/ai-media-format.md

All other details in the registrations remain unchanged.

===

IANA QUESTIONS:

We can update the templates for requests #1 (name) and 3 (spec). Are you OK with request #1, though? Ordinarily, we don't have a problem with using roles or organization names as contacts rather than a person's name, as long as we have the person's name in our records, but that usually comes with an organization-specific email address. I missed the request that we remove his name from "all records," and I'll have to explain that we can't remove his name from our internal records if any of his registration requests are approved. I'll also follow up on his reference to an "alias name," which doesn't work for us, if I understand his meaning correctly.

I wrote back to explain that standards-tree media type registration requires an RFC, submission by/on behalf of an SDO, or approval for registration as a grandfathered type, which would include some documentation/indication of use. His reply: 

"Am a first timer in mime registration, So  normally, I have never came across a mime extension with file_name.prs.extension type, Thats why I sent the update request. If am suppose to start with .prs.aimg after adoption and growth switch to .aimg,
If thats the rule, We cant change the rule so its ok I can start with .prs."

thanks,
Amanda

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]