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

Purpose of terms.md #82

Closed
peterdesmet opened this issue Jan 23, 2015 · 6 comments
Closed

Purpose of terms.md #82

peterdesmet opened this issue Jan 23, 2015 · 6 comments
Assignees
Labels

Comments

@peterdesmet
Copy link
Member

@mdoering, @tucotuco: what is the purpose of this file: https://github.com/tdwg/dwc/blob/dwc_cleanup/terms/terms.md Does it appear on the website?

@mdoering
Copy link
Contributor

I have no idea and only saw that yesterday for the first time. Looks like it came from the documentation?
5b589e3

@tucotuco
Copy link
Member

These were copied from the documentation repository and constitute the
auxiliary documentation on the classes from the Google Code site. This
remains only as a reference until this information can be captured on the
GBIF Media Wiki. Perhaps Éamonn can assess whether this has been done.

On Fri, Jan 23, 2015 at 12:29 PM, Markus Döring notifications@github.com
wrote:

I have no idea and only saw that yesterday for the first time. Looks like
it came from the documentation?


Reply to this email directly or view it on GitHub
#82 (comment).

@tucotuco
Copy link
Member

We can close this issue when the data have been secured on the GBIF Media Wiki, for which Éamonn has taken responsibility.

@tucotuco tucotuco removed this from the Migration of DwC to GitHub milestone Jan 26, 2015
@tucotuco
Copy link
Member

tucotuco commented Feb 5, 2015

From email discussions, I think the consensus is converging on managing all commentary on this Github site, and on producing translations from a simple set of csv files.

JRW:
"I think it might be easiest to have a simple csv file with a column for term name and columns for the translations. We could script combining that with the normative document to produce translated versions. I worry a little about making sure the translation is for the current version. It would be good if the translation was tagged with a term version so we knew unequivocally what it is meant to match. In the translated rdf files (or maybe all in one file) we would include the original normative definitions and comments so that people would always have that as a reference."

Éamonn:
"Hi John,
I agree - we should come up with the simplest possible CSV file making sure the term for translation is versioned.
The attached are some spreadsheets of translations that I used in the past. I exported the Excel files in XML and then transformed them using XSLT, combining all translations into one master RDF file with the original normative definitions. We could probably test this with Japanese as there seemed to be interest when I asked the Japanese Node manager when he was here last week about value of such translations."

I have included the spreadsheets for reference in the resources folder in the dwc_cleanup branch.

@tucotuco
Copy link
Member

Created a corresponding issue on the Darwin Core Question and Answer repository.

@peterdesmet
Copy link
Member Author

Seems like there is no action required for this issue in this repo.

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

3 participants