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.

Sign up for GitHub

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

Jump to bottom

Top and bottom types #94

Closed
nsbgn opened this issue Jun 15, 2022 · 2 comments
Closed

Top and bottom types #94

nsbgn opened this issue Jun 15, 2022 · 2 comments
Milestone
Version 0.2: RDF ...

Comments

@nsbgn
Copy link
Contributor

nsbgn commented Jun 15, 2022 •
edited
Loading

Diverting from issue #79: We need a top and bottom type urgently because it will help us in using types of the form F(_) in queries, since we can just search for a subtype of F(Top) instead.
nsbgn added a commit that referenced this issue Jun 16, 2022
@nsbgn
Add top and bottom type operators (wip).
668e5bc 
See issue #94.

Still need to:

-   Add them to taxonomy.
-   Handle top and bottom types in transformation graphs.
-   Add tests.
-   Replace wildcards in query types with `Bottom`.
@nsbgn
Copy link
Contributor Author

nsbgn commented Jun 16, 2022

Still need to:

  • Add them to taxonomy.
  • Handle top and bottom types in transformation graphs.
  • Add tests.
  • Replace wildcards in query types with Bottom.

@nsbgn nsbgn added this to the Version 0.2: RDF support milestone Jun 16, 2022
nsbgn added a commit that referenced this issue Jun 16, 2022
@nsbgn
Method to iterate sub/supertypes of any type.
42761b0 
This will simplify the generation of type taxonomies, which, in turn,
needs to be modified so that it includes top and bottom types as
described in issue #94.
nsbgn added a commit that referenced this issue Jun 19, 2022
@nsbgn
Change way canonical types are put into taxonomy.
6db50ea 
Simplifications towards issue #94. The `Language.taxonomy` can be
retired soon.
nsbgn added a commit that referenced this issue Jun 19, 2022
@nsbgn
Remove .taxonomy on Languages.
a46b063 
It is now done via canonical nodes, which communicates intent much
better and simplifies working towards #94.

Was announced in commit 6db50ea. See
also the two subsequent commits b2ae9db
and 7b7f4ad.
nsbgn added a commit that referenced this issue Jun 21, 2022
@nsbgn
Optionally add Top and Bottom types to taxonomy.
50eb863 
See issue #94. Untested.

This commit changes behaviour, because all sub- and supertypes in a
lineage must now be canonical --- it is no longer possible to have a
canonical root that has non-canonical supertypes.

Also fixed an issue in `.uri()` that goes along with it,
because it allowed unnamed operators to sometimes not throw an error
when put into the taxonomy.
nsbgn added a commit that referenced this issue Jun 23, 2022
@nsbgn
Add tests for inclusive taxonomy, fix issues w/it.
6daf5a9 
Fixes issue #94. The resulting taxonomy is more complicated than I
imagined, so it will need some testing.
@nsbgn nsbgn mentioned this issue Jun 23, 2022
Closed
@nsbgn
Copy link
Contributor Author

nsbgn commented Jun 23, 2022 •
edited
Loading

Top and bottom types are included. New issue for handling wildcards: #95.

@nsbgn nsbgn closed this as completed Jun 23, 2022
@nsbgn nsbgn mentioned this issue Jun 23, 2022
Closed
nsbgn added a commit that referenced this issue Jun 24, 2022
@nsbgn
Use Top type to handle wildcards in queries.
bd567a3 
Cf. #94, #95, #96.
@nsbgn nsbgn mentioned this issue Jun 25, 2022
Closed
@nsbgn nsbgn mentioned this issue Aug 10, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Version 0.2: RDF support
Development

No branches or pull requests
1 participant
@nsbgn