Closed siuc-nate closed 5 years ago
I have a couple of questions on these. Someone had brought this up yesterday, but in the spreadsheet we have skos:relatedMatch and the google doc/issue has skos:related. In the CaSS editor, we have Related Match, should this be changed to Related or kept as is?
I will need to add ceasn:source to the concept scheme profile of the editor. Which section should it go under (Context, Tagging, etc.)?
Right now we are using skos:relatedMatch. Leaving this open until we confirm one way or the other.
There was a whole thread on skos:related and skos:relatedMatch filled with explanations.
Really all I need to know for now is, which one does this statement pertain to? "Assertion indicating an associative, non-hierarchical relationship between the two concepts where neither is broader nor narrower than the other." We have this as the definition for relatedMatch, but above it is listed as related.
If both should be present in the editor, I would need the definition for the other one as well so that I can add it.
@stuartasutton Yeah, this was a placeholder comment, since we didn't know exactly where that thread was. Was going to link it in here and resolve it one way or the other momentarily.
https://github.com/cassproject/cass-editor/issues/531 has a comment on this.
It looks like skos:related and skos:relatedMatch are both relevant, however, skos:relatedMatch is a specialization (or stronger version) of skos:related.
From the spec:
The property skos:related is used to assert an associative link between two SKOS concepts.
The property skos:relatedMatch is used to state an associative mapping link between two concepts.
This leads me to believe that "Assertion indicating an associative...." definition refers to skos:related.
The SKOS spec does not actually define these terms because they relied on long established practice in thesaurus construction and long standing ISO standards. The following text is mine from an email on March 22 to Jeanne, Michael and Nate:
Guys, sorry if this response is a bit pedantic, but skos has a property called ckos:related that in the world of thesauri construction is for pointing to a term that is semantically related but not in a broader/narrower sense. It has a super property of skos:semanticRelation. There is a property skos:relatedMatch that has super properties skos:mappingRelation AND skos:related. skos:relatedMatch is for pointing to a concept in some other concept scheme that is not just "related", but a close match in terms of identity. The skos:related is for general use for pointing to something that would be considered significantly "related"--e.g., "U.S. Civil War" might be skos:related "Abraham Lincoln" but would certainly not be considered skos:relatedMatch (i.e., they certainly don't share an identity).
Truth be told, our schema should have both. In fact, our context file for concept schemes should include ALL of the skos:properties even though our tool implementation might not (yet).
@stuartasutton Are there official definitions for Concept Scheme and Concept? I wasn't able to find any obvious ones. If we need to come up with something, we will need to do so before I can put these into the system.
I have added and modified the terms as described above in pending CTDL-ASN, using the following (placeholder?) definitions for Concept Scheme and Concept:
Concept Scheme: A controlled vocabulary. Concept: Term in a controlled vocabulary.
These changes have not yet been added to history tracking.
These changes have been made in pending CTDL/CTDL-ASN and noted in the history tracking.
Use this document for reference: https://docs.google.com/document/d/1VLlgPknH_vqhO-VAY39Q7_noJUT3vN_UT1PeTperUiE/edit?usp=sharing
Add SKOS classes:
Add SKOS properties:
Modify CTDL-ASN terms:
Modify CTDL terms: