[media-types] Re: [IANA #1445194] application/vnd.de ut+json registration request

"Murray S. Kucherawy" <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <CAL0qLwZMcQXBZ9gXvyVtegrt3bpwhkRPqZ3SThXgRHpe4uE8hg@mail.gmail.com>
One suggestion and a formatting fix.

On Mon, Mar 2, 2026 at 5:15 PM Amanda Baber via RT <
[email protected]> wrote:

> Name: Yuriy Sydorenko
>
> Email: [email protected]
>
> Media type name: application
>
> Media subtype name: vnd.deut+json
>
> Required parameters: N/A
>
> Optional parameters: N/A
>
> Encoding considerations: 8bit
>
> The format is a structured JSON-based container. Standard JSON encoding
> considerations apply.
>
> Security considerations: The .deut format is a structured JSON-based
> container designed for visual art assets. It stores the user's raw intent
> (input_dna), system parameters, and compiled results (llm_output). The
> format is strictly declarative data and does not contain executable code,
> scripts, or macros. To ensure provenance, integrity, and prevent silent
> tampering, the format includes a built-in cryptographic fingerprint
> mechanism utilizing a SHA-256 hash. Security risks are limited to standard
> JSON parsing vulnerabilities, so parsers must ensure robust handling of
> malformed JSON.
>
> Interoperability considerations: The .deut format acts as a "Digital
> Negative" for generative arts, ensuring non-destructive editing. The schema
> is platform agnostic; while designed for DEUTLI, it is explicitly open for
> implementation by any external tool.


I suggest mentioning here whether there are any older versions of either
applications or the published specification that might lead to
interoperability concerns.


> Published specification: The official specification, validation protocol,
> and schema.json are publicly available in the open-source repository:
> https://github.com/deut-li/open-deut-format.
>
> Applications which use this media: DEUTLI.
>
> Fragment identifier considerations: The syntax and semantics of fragment
> identifiers for this type are as specified for "application/json".
> Additionally, fragment identifiers MAY be used to indicate specific
> elements within the JSON document, following the JSON Pointer syntax
> defined in RFC 6901.
>
> Restrictions on usage: None. This media type is intended for open and
> general use across platforms.
>
> Provisional registration? (standards tree only): No
>
> Additional information:
>
> 1. Deprecated alias names for this type: None
> 2. Magic number(s): None
> 3. File extension(s): .deut
> 4. Macintosh file type code: None
> 5. Object Identifiers: None
>
> General Comments: The .deut format is a structured JSON-based container
> for visual art assets ensuring non-destructive editing and provenance
> tracking via SHA-256 fingerprinting. It acts as the "Digital Negative" for
> generative arts. Unlike simple prompt text files, a .deut file stores the
> raw intent, the system parameters, and a cryptographic proof of integrity.
> This ensures that original user inputs are preserved separately from the
> LLM-generated prompt. While designed for DEUTLI, the schema is open for any
> tool to implement. The full specification and JSON schema are publicly
> maintained at: https://github.com/deut-li/open-deut-format
>
> Person to contact for further information:
>
> 1. Name: Deut.li
> 2. Email: [email protected]
>
> Intended usage: COMMON
>
> Author/Change controller: Author: Deut.li Engineering Team Change
> controller: Deut.li Engineering Team
>

This line seems to be mangled.

-MSK

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.