[media-types] [IANA #1434755] application/vnd.faf+yaml registration request

Hi Alexey,

They've provided revised encoding and "applications which use this media" sections, and they're asking if it's OK to leave the file extension as-is:

===

Encoding considerations: binary

UTF-8 encoding required. Binary content may be base64-encoded within YAML
structure. Lines may exceed 1000 octets due to embedded project metadata.

  ---
Applications which use this media:

  This media type is used by:

  - AI development tools and coding assistants for project context
understanding
  - Command-line interface tools for generating and validating project
metadata
  - IDE extensions and editor integrations for AI-assisted development
  - Browser extensions for extracting project information from repositories
  - Model Context Protocol servers for persistent AI context management
  - CI/CD pipelines for tracking project evolution
  - Development workflow automation tools requiring structured project
metadata

  ---
File extension (.faf):

Our specification requires the exact filename project.faf and its unique path
at project root, alongside package.json, tsconfig.json, and other foundational
configuration files (see attached screenshot).

The specific filename and path requirement combined with the verbose MIME type
application/vnd.faf+yaml provides sufficient disambiguation while maintaining
ecosystem compatibility with 10,067 npm downloads and
official Anthropic MCP integration.

We respectfully request approval to retain the .faf extension as specified.

=====

Is this OK to register?

thanks,
Amanda

On Wed Oct 29 14:29:56 2025, [email protected] wrote:
> Hi Amanda,
> 
> On 27/10/2025 23:19, Amanda Baber via RT wrote:
> > Hi Alexey,
> >
> > Would you be able to review this one by November 10th?
> This is mostly fine, but a few comments/questions below:
> > thanks,
> > Amanda
> >
> > =====
> >
> > Name: James Wolfe
> >
> > Email: [email protected]
> >
> > Media type name: application
> >
> > Media subtype name: vnd.faf+yaml
> >
> > Required parameters: N/A
> >
> > Optional parameters: Format version (e.g., version=1.0)
> >
> > Encoding considerations: 8bit
> If the format can have lines longer than 1000 octets, then Encoding
> should be "binary".
> > UTF-8 encoding required. Binary content may be base64-encoded within
> > YAML structure.
> >
> > Security considerations: Security considerations:
> > .faf files contain project metadata and configuration information.
> > Implementations should:
> > - Validate YAML structure before parsing
> > - Sanitize file paths to prevent directory traversal
> > - Verify score and confidence values are within valid ranges (0-100,
> > 0-1.0)
> > - Not execute code contained in .faf files
> > - Treat content as untrusted user input
> >
> > Privacy: .faf files may contain project-specific information
> > including dependencies,
> > architecture details, and development workflows. Sensitive
> > information should not be
> > included in publicly shared .faf files.
> >
> > Interoperability considerations: Interoperability considerations:
> > .faf extends YAML with specific structure for AI context
> > representation. All .faf files
> > are valid YAML documents. Standard YAML parsers can read .faf files,
> > though specialized
> > parsers are recommended for validation and scoring features.
> >
> > Cross-platform compatibility achieved through:
> > - Platform-agnostic YAML format
> > - UTF-8 encoding
> > - No platform-specific path conventions in core specification
> >
> > Published specification: https://github.com/Wolfe-Jam/faf (primary
> > specification)
> > https://faf.one (documentation and reference implementation)
> >
> > Applications which use this media: - faf-cli: Command-line tool for
> > .faf generation and validation
> > - claude-faf-mcp: Anthropic Model Context Protocol server (official
> > MCP registry)
> > - AI development environments: Claude Code, OpenAI Codex, Google
> > Gemini
> > - IDE integrations: VS Code, Cursor
> > - Chrome Extension for GitHub integration
> This field doesn't need to list specific implementations, but it
> should
> give an idea about types of applications that make use of this media
> type.
> > Fragment identifier considerations: N/A
> >
> > Restrictions on usage: None (MIT License, open source)
> >
> > Provisional registration? (standards tree only): No
> >
> > Additional information:
> >
> > 1. Deprecated alias names for this type: N/A
> > 2. Magic number(s): Files typically begin with YAML structure
> > starting with "version:" key or YAML document marker "---"
> > 3. File extension(s): .faf
> I googled and there are multiple existing uses of .faf extension.
> While
> it is not a requirement for media type registrations to have a unique
> filename extension, it would be the best if this can be changed to be
> unique.
> > 4. Macintosh file type code: N/A
> > 5. Object Identifiers: N/A
> >
> > General Comments: .faf is designed as a universal format for AI
> > project context representation across all development environments
> > and AI platforms. Current adoption includes official integration with
> > Anthropic's Model Context Protocol ecosystem, 9,900+ npm package
> > downloads, and validation across major AI platforms (Claude, OpenAI
> > Codex, Google Gemini). The format addresses fundamental AI context
> > incompleteness in software development workflows.
> >
> > Person to contact for further information:
> >
> > 1. Name: Wolfe James
> > 2. Email: [email protected]
> >
> > Intended usage: COMMON
> >
> > Author/Change controller: Wolfe James
> > Creator and Maintainer, .faf Format Specification
> > Email: [email protected]
> > ORCID: 0009-0007-0801-3841
> > GitHub: https://github.com/Wolfe-Jam/faf
> 
> Best Regards,
> 
> Alexey

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