Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.diggsml file extension #32

Open
nickmachairas opened this issue Sep 21, 2022 · 5 comments
Open

.diggsml file extension #32

nickmachairas opened this issue Sep 21, 2022 · 5 comments

Comments

@nickmachairas
Copy link
Member

Has it ever been considered officially adopting a file extension other than .xml for DIGGS files? Such as .diggsml, .dgsml, or similar. It would be a small but significant improvement for programs that identify, create and parse DIGGS files.

@panars
Copy link
Contributor

panars commented Sep 25, 2022

I do not remember it being discussed before. I searched and there are some other xml schemas that use a different file extension, such as MusicXML (.mxl), .mathml, .gml, and .kml . The benefit would be automatically opening a DIGGSML file with an associated program.

@sdeaton75
Copy link
Collaborator

I agree - it definitely would have the benefit being able to be opened automatically/recognized as a DIGGS file without having to open it and is fundamentally a good suggestion.

@dponti
Copy link
Collaborator

dponti commented Nov 4, 2022

I like this idea but am not personally a fan of file extensions that are longer than 4 characters, although we may not have much choice if we want to create a unique but recognizable extension as ones I would normally think of, such as .dgml, .dml, .dxml .dsml and .diml are already in use (although it is not uncommon for different file types to use the same extension).

Perhaps this thread can generate some discussion on appropriate extension names? I'm ok with either of Nick's suggestions but perhaps .dgsml would be better as it's shorter.

@panars
Copy link
Contributor

panars commented Nov 6, 2022

While 3 or 4 characters are pretty typical for file extensions, there are plenty of extensions with more than 4 characters. ACCDB and BLEND are two that come to mind. I think if we shorten it too much it may cause more confusion. My feeling is that it is okay to be longer than 4 characters if it helps clarify what the file is for. Does it have to include "ml" for markup language? I tend to think not. I like just plain ".diggs" because that is how we have been talking about these files anyway, e.g. "Can you convert that to a DiGGS file?"

@sdeaton75
Copy link
Collaborator

I agree with Peter - I would just go with .diggs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants