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

Artifact.uri referring to a table in a TAP service #179

Open
pdowler opened this issue Jun 7, 2024 · 2 comments
Open

Artifact.uri referring to a table in a TAP service #179

pdowler opened this issue Jun 7, 2024 · 2 comments
Labels

Comments

@pdowler
Copy link
Member

pdowler commented Jun 7, 2024

This is technically possible, but we should define a common practice for the URI structure so that other users can, in principle, understand the URI and do something useful.

@pdowler pdowler added the TBD label Jun 7, 2024
@pdowler
Copy link
Member Author

pdowler commented Jun 7, 2024

naively, if there is a table named my_project.my_stuff in a TAP service with registry identifier ivo://example.net/cat then a URI for the table might be

ivo://example.net/cat?my_project.my_stuff

where the implicit assumption is that objects in a TAP service are the tables. The bit after the ? would need to be more elaborate to denote schemas, tables, etc.... maybe

ivo://example.net/cat?schema_name=my_project
ivo://example.net/cat?table_name=my_project.my_stuff

where schema_name and table_name are keys defined in the TAP spec.

@pdowler
Copy link
Member Author

pdowler commented Jun 7, 2024

further complication:

A single table in a TAP service may have records from multiple Artifact(s) in CAOM, so the Artifact.uri could/should refer to a set of records in that table... that could be quite complex in the general case. TBD

@pdowler pdowler changed the title Artifact.uri referrig to a table in a TAP service Artifact.uri referring to a table in a TAP service Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant