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

rephrase data type requirements #15

Merged
merged 1 commit into from Jan 29, 2021

Conversation

mbtaylor
Copy link
Member

Report the requirements for per-column data types in terms of
their VOTable encoding (datatype, arraysize and xtype attributes)
rather than their database types, since the choice of database type,
especially at TAP 1.1, is purely an implementation detail.

Also ensure that the s_region type is compatible with DALI regions.

Report the requirements for per-column data types in terms of
their VOTable encoding (datatype, arraysize and xtype attributes)
rather than their database types, since the choice of database type,
especially at TAP 1.1, is purely an implementation detail.

Also ensure that the s_region type is compatible with DALI regions.
@mbtaylor
Copy link
Member Author

I suggest some change along these lines to clarify the requirements in terms of the output data types. Authors are welcome to adjust the wording and formatting etc.

@jesusjuansalgado jesusjuansalgado merged commit 53dc494 into ivoa-std:master Jan 29, 2021
@mbtaylor mbtaylor deleted the datatypes branch January 29, 2021 14:55
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

Successfully merging this pull request may close these issues.

None yet

2 participants