You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In new controlled vocabularies, we are trying to avoid spaces and non-alphanumeric characters. That often takes the form of lower camelCase of an English phrase since it follows that rule and has consistent capitalization.
In Camtrap DP we currently use lower case values with spaces for controlled vocabularies (defined in enum properties). Should we aim to use camelCase here too (before releasing v1.0)? Our term names are already in camel case. The change would only affect controlled values with more than one word, single words would remain the same.
The text was updated successfully, but these errors were encountered:
# samplingDesignsimple random → simpleRandomsystematic random → systematicRandomclustered random → clusteredRandom# captureMethodmotion detection → motionDetectiontime lapse → timeLapse# featureTyperoad paved → roadPavedroad dirt → roadDirttrail hiking → trailHikingtrail game → trailGameroad underpass → roadUnderpassroad overpass → roadOverpassroad bridge → roadBridgenest site → nestSitewater source → waterSourcefruiting tree → fruitingTree# rolesrightsholder → rightsHolderprincipal investigator → principalInvestigator
Note: 2 borrowed terms (relationType and resourceTypeGeneral) also borrow their controlled vocabulary which has UpperCamelCase values. I would leave those as is.
This pattern has been followed pretty consistently as new controlled vocabularies have been created. There are a few exceptions in cases:
-where there were existing suggested values that we didn't want to break
in cases where the controlled value strings represented classes and the pattern had been to use the term local names (which were in UpperCamelCase).
Just for full disclosure, there was never any formal decision by the TAG or any other group that established this pattern. I suggested it when the first controlled vocabularies were created in DwC (establishmentMeans, pathway, and degreeOfEstablishment) as a way to reduce the number of possible variants that people could dream up and as a way to clearly distinguish between labels (non-normative and potentially multilingual) and controlled values (normative and invariant among languages). So it's become established as a pattern for controlled value stings in subsequent controlled vocabularies since then. I think that there is value in maintaining these patterns so that the required values are what people have come to expect if they've had experiences with other vocabularies.
In tdwg/dwc-qa#169 (comment) @baskaufs writes:
In Camtrap DP we currently use
lower case
values with spaces for controlled vocabularies (defined inenum
properties). Should we aim to use camelCase here too (before releasing v1.0)? Our term names are already in camel case. The change would only affect controlled values with more than one word, single words would remain the same.The text was updated successfully, but these errors were encountered: