-
Notifications
You must be signed in to change notification settings - Fork 72
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
Decide where to define "status" #165
Comments
I opened an issue on the TAG tracker about this several days ago: tdwg/tag#13 but haven't gotten any comments about it yet. I feel as though these properties should apply TDWG-wide and therefore should not be part of DwC per se. The Documentation Spec has already coopted this namespace to define two new terms that aren't specifically about DwC. |
OK, let's close this issue once it's picked up there. |
Comment about |
@baskaufs can this be closed? |
I think we can close this. All of the tdwgutility: terms (rebranded to be TDWG-wide) can be viewed here: |
As noticed in #153, we will remove
dwc_attributes.rdf
: https://github.com/tdwg/dwc/blob/64311240eeb15c0016c858846f9adbfb91bd515d/terms/dwc_attributes.rdf. It definesstatus
,decision
,abcdEquivalence
, andorganizedInClass
. The last two have been moved out of the standard, but thestatus
and maybedecision
(see #164) need to be defined somewhere. Where do we want keep this? @baskaufs @tucotucoThe text was updated successfully, but these errors were encountered: