Changes between Version 13 and Version 14 of Taskforces/Curation/ValueNormalization
- Timestamp:
- 02/14/19 13:33:35 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Taskforces/Curation/ValueNormalization
v13 v14 294 294 We should also take into account that the CMDProfile usually encodes a resource type (collection, !TextCorpus, !BilingualDictionary, etc.). 295 295 296 There is also an elaborate [[#D5C-2|LRT-Taxonomy]] (Carlson et al. 2010) made by us(!) - I mean CLARIN people, as one of the first deliverables of CLARIN back in 2010. In search for a starting point, it may be worth to have a look at that. An initiative outside CLARIN that could be relevant is the [http://vocabularies.coar-repositories.org/documentation/resource_types/ 1.0/COAR resource type vocabulary].296 There is also an elaborate [[#D5C-2|LRT-Taxonomy]] (Carlson et al. 2010) made by us(!) - I mean CLARIN people, as one of the first deliverables of CLARIN back in 2010. In search for a starting point, it may be worth to have a look at that. An initiative outside CLARIN that could be relevant is the [http://vocabularies.coar-repositories.org/documentation/resource_types/ COAR resource type vocabulary]. 297 297 298 298 Ad-hoc attempt for a mapping values between the three related(?) data categories: