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

Export as Turtle doesn't use common .ttl file extension #146

Closed
nicholascar opened this issue Jul 31, 2021 · 3 comments
Closed

Export as Turtle doesn't use common .ttl file extension #146

nicholascar opened this issue Jul 31, 2021 · 3 comments
Assignees
Milestone

Comments

@nicholascar
Copy link

All Export Ontology resultant files seem to end in .owl, regardless of the format selected. For Turtle files it's typical to use .ttl, not .owl.

@mnamici
Copy link
Collaborator

mnamici commented Oct 29, 2021

Hi, I've started addressing this issue in #163, that has already been merged for the next release which will be out soon.
Essentially with this change if you explicitly specify any of the recommended owl 2 file extensions from the export file dialog then there will be no '.owl' extension appended to the file.
The list of file extensions currently recognized are:

  • .owl - which is mostly a legacy from the old owl 1 spec
  • .ofn - as recommended for owl 2 functional-style syntax files
  • .owx - as recommended for owl 2 xml syntax
  • .omn - as recommenmded for owl 2 manchester syntax
  • .ttl - as recommended for RDF turtle notation

Notice however that the preferred extension must be specified by the user and is not automatically related to the syntax used in the exporter, so I'm not sure this change addressed this issue entirely. As an alternative we could look for the user-suggested file extension and preset the most appropriate syntax in the exporter.

@mnamici mnamici self-assigned this Oct 29, 2021
@mnamici mnamici added this to the Eddy 3.2 milestone Oct 29, 2021
@nicholascar
Copy link
Author

As long as it always works the same ever time, it probably doesn't matter which way you do it! So either implementation of the format selection dictates file extension or fie extension selection (typed in) dictates format would work.

@mnamici
Copy link
Collaborator

mnamici commented Nov 24, 2021

Given the current export workflow (file selection -> syntax and axiom selection) I think the latter is currently more intuitive.
I recently merged this in #165.

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

3 participants