-
Notifications
You must be signed in to change notification settings - Fork 5
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
Are Camtrap DP terms narrower or same as referenced terms from other standards? #288
Closed
51 tasks done
Comments
Thanks John, I've updated those 6 relations in 5da2692. |
4 tasks
Addressed in Camtrap DP 0.6 #297. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@baskaufs @tucotuco
Issue
Camtrap DP terms link to terms described in other standards (DwC, DC, AC, ...) to help users crosswalk. The relation can be described as:
broadMatch
of Camtrap DP termexactMatch
of Camtrap DP termnarrowMatch
of Camtrap DP termSince Camtrap DP has a limited scope (it's about camera trap datasets), should we always indicate the links as
broadMatch
to Camtrap DP term? Or is it fair to useexactMatch
sometimes?Examples
bibliographicCitation
scientificName
eventID / deploymentID
decimalLatitude / latitude
All current relations
Package
skos:exactMatch
of bibliographicCitationskos:broadMatch
of samplingDesignskos:exactMatch
of coordinatePrecisionskos:exactMatch
of spatialskos:exactMatch
of temporalskos:exactMatch
of taxonIDskos:exactMatch
of scientificNameskos:exactMatch
of taxonRankskos:exactMatch
of kingdomskos:exactMatch
of phylumskos:exactMatch
of classskos:exactMatch
of orderskos:exactMatch
of familyskos:exactMatch
of genusskos:exactMatch
of vernacularNameskos:exactMatch
of relationTypeskos:exactMatch
of resourceTypeGeneralskos:exactMatch
of relatedIdentifierTypeDeployments
skos:broadMatch
of deploymentIDskos:exactMatch
of locationIDskos:exactMatch
of locationNameskos:exactMatch
of latitude Changed to skos:broadMatch in 5da2692skos:exactMatch
of longitude Changed to skos:broadMatch in 5da2692skos:exactMatch
of coordinateUncertaintyskos:exactMatch
of start Changed to skos:broadMatch in 5da2692skos:exactMatch
of end Changed to skos:broadMatch in 5da2692skos:broadMatch
of setupByskos:broadMatch
of cameraModelskos:exactMatch
of habitatskos:narrowMatch
of tags Changed to skos:exactMatch in 8c25523skos:exactMatch
of commentsMedia
skos:broadMatch
of mediaIDskos:broadMatch
of deploymentIDskos:broadMatch
of eventIDskos:broadMatch
of captureMethodskos:exactMatch
of timestampskos:broadMatch
of filePathskos:exactMatch
of commentsObservations
skos:exactMatch
of observationID Changed to skos:broadMatch in 5da2692skos:broadMatch
of eventIDskos:exactMatch
of taxonIDskos:exactMatch
of scientificNameskos:exactMatch
of countskos:exactMatch
of lifeStageskos:exactMatch
of sexskos:exactMatch
of behaviorskos:exactMatch
of individualIDskos:exactMatch
of classifiedByskos:exactMatch
of classificationTimestamp Changed to skos:broadMatch in 5da2692skos:exactMatch
of tagsskos:exactMatch
of commentsThe text was updated successfully, but these errors were encountered: