I wanted to create a file format for describing nests of files for ease of access with my application. I discovered the extension I thought of to go with my naming scheme was in use by a megacorporation for one of their many pieces of software. What liability would I face for using this file extension, and would it be better to adjust it than attempt to solve any future conflicts?
Worry a lot :) your extension might just wrongly open with an wrong Software because it's associated/linked just to that program. Like .doc is linked to Word.
So it's better to choose w unique extension. Since we're out of 8.3 era - nothing holds you from the 8.4 or xxx.5 scheme.
The only thing is to keep an eye onto what filesystems can take. NTFS is suitable for 256 characters, but I'm not sure if the dot and extension is within this maximum or not.
I have a tool (MindNode) that thinks ".md" is supposed to belong to it
Which is stupid
Because markdown has been using ".md" for far longer than MindNode's been around
But c'est la vie - I just make sure I have ".md" associated with my markdown editor of choice, and force MindNode to only open files through File->Open
Hi, I am one of the engineers working on MindNode. We don’t register MindNode as the owner of “md”, but as an app that can open and save to this file type. If we don’t do this we are unable to import and export Markdown files. You can change the default app anytime in Finder by using “Get Info (cmd+i)” and choose an app in the “Open with:” section of the Info window. If you need further assistance, please contact us via "Send us an Email" on https://www.mindnode.com/support
So it's better to choose w unique extension. Since we're out of 8.3 era - nothing holds you from the 8.4 or xxx.5 scheme. The only thing is to keep an eye onto what filesystems can take. NTFS is suitable for 256 characters, but I'm not sure if the dot and extension is within this maximum or not.