[media-types] [IANA #1458437] text/prs.zcoe registrati on request

"Amanda Baber via RT" <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <[email protected]>
Hi Alexey,

Can you review this one by September 4th?

This is the personal-tree request I referred to yesterday. We have the applicant's name (not the same person as the other request), but they don't want to include it in the registration form. Does this work? If not, what if we added something like "(Name provided to IANA)" in the contact name field?

thanks,
Amanda

===

Media type name: text

Media subtype name: prs.zcoe

Required parameters: N/A.

Optional parameters: N/A.

Encoding considerations: 8bit

Security considerations: 1. ZCOE source files are plain text source code files. They do not contain active or executable content in the media type itself. However, ZCOE source code may be compiled and executed, and as such, it may contain arbitrary code. Users SHOULD exercise the same precautions when handling ZCOE source files as they would with any other source code file (e.g., .c, .h). The ZCOE compiler/interpreter is responsible for ensuring safe compilation and execution of the code.

2. The media type itself does not contain privacy or integrity-sensitive information. Any privacy or integrity concerns are dependent on the content of the source code. If such protection is needed, it should be provided externally through appropriate mechanisms, such as access control, encryption, or digital signatures (e.g., SSL/TLS, PGP).

3. N/A (no built-in privacy/integrity services).

4. This media type does not use XML, JSON, compression, or container formats. It is a plain text source code format.

5. The media type does not incorporate external links or references that are required for interpretation.

Conclusion: Security risks associated with text/prs.zcoe are similar to those of other plain text source code media types (e.g., text/x-c). Users should apply standard security practices for handling source code.

Interoperability considerations: There are no known interoperability issues.

Published specification: A formal specification is under development and will be made publicly available upon project release.

Applications which use this media: ZCOE compiler and related development tools. ZCOE is a lightweight C superset with namespace isolation, dependency management, and OOP support. The compiler processes .zcoe files and generates C code.

Fragment identifier considerations: N/A.

Restrictions on usage: N/A.

Provisional registration? (standards tree only): No

Additional information:

1. Deprecated alias names for this type: N/A.
2. Magic number(s): N/A.
3. File extension(s): .zcoe
4. Macintosh file type code: N/A.
5. Object Identifiers: N/A.

General Comments: ZCOE stands for "ZCOE C OOP Extension" (recursive acronym). The project is currently in testing/development phase.

Person to contact for further information:

1. Name: tntxxd
2. Email: [email protected]

Intended usage: COMMON

Author/Change controller: tntxxd ([email protected])

_______________________________________________
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.