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

Some changes to consider #2

Open
jamesaoverton opened this issue Mar 19, 2024 · 0 comments
Open

Some changes to consider #2

jamesaoverton opened this issue Mar 19, 2024 · 0 comments

Comments

@jamesaoverton
Copy link
Member

jamesaoverton commented Mar 19, 2024

Here are some changes to LDTab format that we're considering making, and some brief notes on our thinking. The changes I'm more certain about are at the top -- less certain at the bottom:

  • change "retraction" to boolean: currently it's "0" or "1" which I find confusing
  • change "retraction" to "retracted": better match for a boolean value
  • use JSON arrays for RDF lists: this is closer to Turtle and more concise, implementation here https://github.com/ontodev/ldtab.clj/tree/rdf-lists
  • rename "assertion" to "transaction": a better name, but "transaction" is a SQL keyword
  • rename keywords in "datatype" column: I'm just unhappy with '_IRI' etc. -- I don't like the underscores. Should they be CURIEs? No, they're keywords. Drop the underscore? We want them to be visually distinct from CURIEs and language tags.
  • rename "annotation" column to "meta": the column is used for both RDF reifications and OWL annotations, so "annotation" might be misleading; on the other hand, we might be overloading the meaning of "meta", using it three different ways in LDTab
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

1 participant