jlevy / jlevy/sidematter-format

Thought - is dropping the final extension desirable?

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
5
Forks
2
PR merge metrics
No merged PRs in 30d

Description

I like this project, it seems sensible to have an agreed format for this :)

The issue that jumps out to me is that, as far as I understand, the format would not support having files with the same basename but different extensions? e.g. `example.txt` and `example.md` would both have a metadata file name of `example.meta.yml`?

I'd therefore suggest it's preferable not to drop the final extension.

As a similar example, AWS Bedrock Knowledge Bases appends `.metadata.json` to the full filename including the extension (image from https://aws.amazon.com/blogs/machine-learning/multi-tenancy-in-rag-applications-in-a-single-amazon-bedrock-knowledge-base-with-metadata-filtering/ ).
![](https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2025/03/26/ML-16728-second.png)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.