[media-types] Re: [IANA #1445923] text/vnd.vri regis tration request

"Murray S. Kucherawy" <[email protected]> Tue, 14 Apr 2026 08:47:29 -0700
Newsgroups gmane.ietf.types
Message-ID <CAL0qLwbuJpGw9kHStMqEhgyC2jZKxFBEZRjzgQPVDzvfFpewyg@mail.gmail.com>
One very minor thing.  Application is approved with this change if the
author accepts.

-MSK

On Thu, Mar 19, 2026 at 8:51 AM Amanda Baber via RT <
[email protected]> wrote:

> Hi Murray,
>
> Would you be able to review a pair of new tickets by April 2nd? This is #1
> of 2.
>
> thanks,
> Amanda
>
> =====
>
> Name: Huynh Canh Duong
>
> Email: [email protected]
>
> Media type name: text
>
> Media subtype name: vnd.vri
>
> Required parameters: N/A
>
> Optional parameters: charset: Specifies the character encoding used in the
> source file. UTF-8 is recommended and expected in most cases.
>
> Encoding considerations: 8bit
>
> Security considerations: This media type represents source code written in
> the Vir programming language.
>
> The content is textual and does not itself execute automatically. However,
> when processed by a compiler, interpreter, or other tooling, the code may
> perform arbitrary actions depending on the implementation and runtime
> environment.
>
> Applications that accept or process this media type SHOULD treat the
> content
> as untrusted input and apply appropriate sandboxing or validation when
> compiling or executing it.
>

BCP 14 isn't active here, so please change this to just "should".


> No inherent security mechanisms are defined by this media type. Security
> considerations therefore depend on the behavior of the compiler, runtime,
> and execution environment.
>
> Interoperability considerations: This media type represents source code
> written in the Vir programming language.
> The content is textual and typically encoded using UTF-8.
>
> Files of this type are intended to be processed by Vir compilers,
> interpreters,
> and development tools. The format is platform-independent and may be
> exchanged
> between systems without modification as long as a compatible Vir toolchain
> is
> available.
>
> No transport or container-specific requirements are imposed by this media
> type.
>
> Published specification: Vir Programming Language Specification.
>
> Available at:
> https://dev.virgori.com/spec
>
> Applications which use this media: This media type is used for source code
> written in the Vir programming language.
>
> Applications that may use this media type include Vir compilers,
> interpreters,
> language servers, build tools, and integrated development environments
> (IDEs)
> that support the Vir language.
>
> Examples include the Vir compiler toolchain, development environments, code
> editors with Vir syntax highlighting, and automated build or analysis
> systems
> that process Vir source files.
>
> Fragment identifier considerations: N/A
>
> Restrictions on usage: None.
>
> Provisional registration? (standards tree only): Yes
>
> Additional information:
>
> 1. Deprecated alias names for this type: N/A
> 2. Magic number(s): N/A
> 3. File extension(s): .vri .sci .svi .vsib
> 4. Macintosh file type code: N/A
> 5. Object Identifiers: N/A
>
> General Comments: The Vir programming language is a modern systems and
> application programming
> language designed for clarity, explicit control flow, and modular
> structure.
> Files with the ".vir" extension contain source code intended to be
> processed
> by Vir compilers and development tools.
>
> This registration is intended to support consistent identification of Vir
> source files across editors, development environments, version control
> systems, and network transports.
>
> Person to contact for further information:
>
> 1. Name: Huynh Canh Duong
> 2. Email: [email protected]
>
> Intended usage: COMMON
>
> Author/Change controller: Vir Programming Language Project
> https://virgori.com
>

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