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

TG2 - Link to Specification Source Code #165

Open
ianengelbrecht opened this issue Sep 4, 2018 · 5 comments
Open

TG2 - Link to Specification Source Code #165

ianengelbrecht opened this issue Sep 4, 2018 · 5 comments
Labels

Comments

@ianengelbrecht
Copy link
Collaborator

Hi all, thanks for the opportunity to participate. In line with @mjcollin's initiative to develop implementation libraries (#150), would it be of any value to include pseudocode in the specification table for each test rather than a link to a specific implementation? As I understand it we're hoping to develop in a number of languages so it might be good to have a common pseudocode reference to use.

@mjcollin
Copy link
Collaborator

mjcollin commented Sep 4, 2018

I think that was discussed at one point (I've only recently taken over our participation in this effort) and the feeling was that it'd be more direct to write a primary implementation in one language with any additional languages using that as a reference. I'd let @ArthurChapman or @chicoreus weigh in though.

@chicoreus
Copy link
Collaborator

@ianengelbrecht, yes it would be of great value to add a pseudocode specification to each test. The TG1 framework includes an element for specification that could contain this, we haven't yet actually framed such a specification for any of the tests, and pseudocode would be a very good way to do this.

@chicoreus
Copy link
Collaborator

To be more explicit: "Specification" has a formal meaning in the TG1 framework. A validation method, measurement method, and enhancement method (and problem method) all compose a specification with a (dimension,criterion,enhancement) in context. Where what we have specified so far in the TG2 test descriptions is at the level of dimension/criterion/enhancement in context. Adding a specification to an X in context moves from the description of general concepts to the level of data quality solutions. See the TG1 Framework Cheat Sheet in the wiki.

@ArthurChapman
Copy link
Collaborator

@chicoreus @Tasilee I am wondering if using pseudocode (with links to actual implementations) would be suitable for a TDWG Best Current Practices Document to document the tests? Just a thought

@Tasilee
Copy link
Collaborator

Tasilee commented Sep 5, 2018

As previously raised, I think it may be expedient to use @chicoreus code as the base due it being largely done. In theory, pseudocode would be nice and this was the original idea.

@chicoreus chicoreus added the TG2 label Sep 6, 2018
@chicoreus chicoreus changed the title Link to Specification Source Code TG2 - Link to Specification Source Code Sep 6, 2018
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

5 participants