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

International Code of Phytosociological Nomenclature #20

Open
mdoering opened this issue May 13, 2020 · 7 comments
Open

International Code of Phytosociological Nomenclature #20

mdoering opened this issue May 13, 2020 · 7 comments
Labels

Comments

@mdoering
Copy link

Is it in scope to include the International Code of Phytosociological Nomenclature and its governed syntaxon names in NOMEN? They can look an awful lot like Linnean names:

https://www.geobotany.org/library/pubs/WeberHE2000_jvs_739-768.pdf

Examples:
https://de.wikipedia.org/wiki/Rotbuchenwald#Gliederung_der_Rotbuchenwälder
https://lfu.brandenburg.de/cms/media.php/lbm1.a.3310.de/9110.pdf
http://www.natura2000.rlp.de/steckbriefe/index.php?a=s&b=l&pk=9130

@mdoering
Copy link
Author

@mjy
Copy link
Member

mjy commented May 13, 2020

IMO any a) formalized and b) international standard for how names for biological entities are governed is a possible inclusion.

@hlapp
Copy link
Contributor

hlapp commented May 13, 2020

That would include the PhyloCode too, no?

@mdoering
Copy link
Author

... and the BioCode

@mjy
Copy link
Member

mjy commented May 13, 2020

Yes to both. From my understanding the BioCode in particular is an example of trying to munge everything together, so adding classes for it making them subclasses of existing NOMEN classes may be informative.

Assertions in the PhyloCode are somewhat orthogonal to those in current codes, so in some ways it might be easier to represent concepts there as seperate classes- I think maybe you do this already somewhere in an ontology @hlapp (brain is foggy)?

@proceps
Copy link
Contributor

proceps commented May 13, 2020

Well, there is also Linz Zoocode, which is an alternative to ICZN.

@hlapp
Copy link
Contributor

hlapp commented May 13, 2020

Assertions in the PhyloCode are somewhat orthogonal to those in current codes, so in some ways it might be easier to represent concepts there as seperate classes- I think maybe you do this already somewhere in an ontology @hlapp (brain is foggy)?

Yes, we are developing an Ontology of Phylogenetic Clade Definitions, if that's what you mean. It is not meant to be a mirror of PhyloCode names, though; rather a superset.

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

4 participants