-
Notifications
You must be signed in to change notification settings - Fork 7
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
TG2-Issues toward the standard #193
Comments
From @chicoreus in regards interpreting values: "Test implementations MAY accept all parameters as strings. The test Specifications include the phrase "interpreted as" to indicate to implementors that data type conversion from string serializations of Darwin Core may be needed. The test descriptions are agnostic to where type conversion is performed in an implementation." |
From our Zoom discussion, we have some of the basic resources
|
We have started writing a standards document and have most of the outline of the structure and some content. We could use this Issue as a publicly exposed area for comments about this document. I will add a comment that exposes the current structure.. |
… artifacts for the draft standard maintained from csv, markdown template, and yaml files with python build scripts paralelling those of DarwinCore. Relates to issue #193.
…for framework vocabulary from ffdq to bdqffdq. Relates to issue #193.
I thing we can close this one, replaced by #300 |
This is a list of issues and associated discussion to bring the work of TG2 to a TDWG standard.
The text was updated successfully, but these errors were encountered: