ensure that dwcattributes:status is set to current in hispidterms.rdf

AaronWilton commented 8 years ago

ensure that dwcattributes:status is set to current in hispidterms.rdf where appropriate

may still some terms that have been ratified with status = new.

nielsklazenga commented 8 years ago

This means that #36 can be closed.

AaronWilton commented 8 years ago

what is our vocabulary for status?

are we using

discouraged [hmmm can understand that feeling ;-).. But seriously, do we need this as a status, why not just in the note - the concept is available for use - period!]
new [since when?? when does it become old?]
proposed [for what?? ;-) ]
under consideration [for what addition, removal, updating]
recommended
current

not sure these are all useful/clear etc...

how about (strawman)

proposed for removal
proposed for addition
under review
current or available or ?recommended

just want clarity and consistency :-(

nielsklazenga commented 8 years ago

Let's not use 'discouraged'. We do that in a comment.
I think 'recommended' is what Darwin Core uses? If so, let's use that.
I am not sure if we would use 'proposed for removal' and 'proposed for addition'. We would only make the changes to the RDF after the proposal has been accepted, right? Or is this for when we put the draft RDF in the issue?

AaronWilton commented 8 years ago

Teleconference 2016-02-12: under review, recommended, (deprecated or equivalent from dwc)

AaronWilton commented 8 years ago

FROM DWC attributes rdf: Values for this term should be either "recommended" or "historical".

nielsklazenga commented 8 years ago

So 'historical' for deprecated. Works for me.

AaronWilton commented 8 years ago

updated.

AaronWilton commented 8 years ago

hmm - see that DWC doesn't even follow it's own standard - they are also using the term superseded in the history file

laurencepaine commented 8 years ago

If I saw the word historical I'm not sure that I would associate that with either deprecated or superseded (ie. I would still assume I could transfer the term, but that some upfield processing would occur to manipulate the value to a different model)

Is that what we want people to think? Can I suggest that the term we want is "DeprecatedOrSuperseded" - no ambuguity then!

AaronWilton commented 8 years ago

oh - just found they are using deprecated in the history too... :-(

so dug a bit further and found this: http://rs.tdwg.org/dwc/terms/namespace/index.htm#classesofchanges

Status (recommended, superseded, or deprecated)

To me superseded is not synonymous with deprecated - the three terms makes more sense to me...

laurencepaine commented 8 years ago

OK. Having read the classesofchanges I see the intent of recommend, superseded and deprecated and agree that this does work. Happy to support all three terms now. Probably need to make sure our own documenation is really clear about this, as we could be having this same debate again in the future quite easily.

nielsklazenga commented 8 years ago

I thought we'd mentioned the 'discouraged' terms in this issue, but I can't find it. Anyway, I have added the discouraging comments to the relevant fields, so you can go ahead and remove the 'discouraged' status, if that hasn't already been done. Since the status will now be 'recommended' I have made sure to only "discourage" the free-text usage.

nielsklazenga commented 8 years ago

Ah, found it...

hiscom / hispid

ensure that dwcattributes:status is set to current in hispidterms.rdf #96