SEKO

Classfication

Hornbostel-Sachs

The original German version of the classification was translated into Finnish and published by Leisiö in 1974.

Availability

Finnish versions

MIMO versions

SEKO with classification

Consider including Hornbostel-Sachs classification as a separate scheme in seko: in scheme:sekoHS ; skos:isTopConcpet ;

  1. Idiofonit (itsesoivat soittimet)
  2. Membranofonit (kalvosoittimet)
  3. Aerofonti (ilmasoittimet)
  4. Kordofonit (kielisoittimet)
  5. Elektrofonit (sähkösoittimet)

Best option would seem to create a new translation in Finnish based on the MIMO version of the classification. Basic terminology would be the same as with Leisiö, but many of the descriptions have been expanded and there was an effort to decrease of the 1914 German cultural skewness. (e.g. removing “eskimoes and negroes”).

Another option would be label the groups as “Instrument families” with more general terms used by MIMO Collections instrument families (these are in principle the H-S classes but without the notations). Remember that these often cover only “Western music” instruments while H-S tries to cover everything. See also https://en.wikipedia.org/wiki/Organology

One optional solution could be to use these as a “type” subClasses of seko:Instrument

Source: VT: Musicdictionary (archived)

Preliminary activities and preparation

Decisions

Schema, namespace, notation and identifiers

The scheme could be used by SEKO3 either

Data

Will need to consult with Finto-team concerning the application on the Finto Skosmos server.

Class differences

Possible coding in SEKO3

seko: the ConceptScheme . # tHe instruments (browsing) sekoHS: Collection-hierarchy # the H-S groups (Group-based browsing, like YSO-groups but with group hierarchy)

sekoHS:1 a skos:Collection, skos-thes:ConceptGroup ;   
  skos:prefLabel "Idiofonit"@fi ;
  skos:notation "1"^^seko-meta:HSNotation ;
  skos:inScheme sekoHS:
  rdfs:seeAlso  hornbostelandsachs:1  ;  
  skos-thes:subGroup sekoHS:57, sekoHS:6204, sekoHS:2, sekoHS:83, sekoHS:70, sekoHS:6209 ;
  skos:member seko:00627 ;

Note! MIMO classification scheme models the relationship from the classification class to the instruments in the other schema with skos:exactMatch. which might not be the correct way? Using groups and member: relationships might be a safer way.

Possible Skosmos configuration for two hiearchies

Using specified notation types for classifications

For groups - perhaps also with instruments

Usage example 1: for a group

sekoHS:228 a skos:Collection , iso-thes:ConceptGroup ;
    skos:inScheme seko:HS ;
    skos:notation "412"^^seko-meta:HSNotation ;
    skos-thes:superGroup sekoHS:226 ;
    rdfs:seeAlso hornbostelandsachs:228 ;
    skos:prefLabel "Yksinkertaiset kordofonit"@fi .

Usage example 2: for an instrument using Bibframe entities

create an issue for this

The “standard” method is to use dct:subject for classifications. This is an ObjectType property, so cannot just enter a string. But we would need a way to express the class notation in the instrument UI and the YKL notations are in skos:notation only, not in the prefLabel.

Example: Thee ways to code the classification of an instrument

seko:00393 a skos:Concept, seko:Instrument ;

# 1  "most general" - notation is already embedded in prefLabel
     dct:subject sekoHS:228 ;             

# 2 Using bibframe style   - uses local groups with notations

     bf:classification [
              a bf:Classification ; 
              bf:code "412.12"^^seko-meta:HSNotation ; 
              bf:source seko:HSScheme ; 
              rdfs:seeAlso seko:h228 ;  # different type!
     ] ; 

# 3 How to use  external classfications ?

     dct:subject [
              a bf:Classification ; 
              bf:code "78.71"^^seko-meta:YKLNotation ; 
              bf:source <http://urn.fi/URN:NBN:fi:au:ykl:78.71> ; 
     ]  .

This would seem to be much easier to accomplish in data entry design but the notations are not of the instrument, but for the class/group it belongs to.

seko:00393
    skos:notation  "412.12"^^seko-meta:HSNotation, "78.71"^^seko-meta:YKLNotation .

In case no Finnish language classification is accomplished

Easy solution would be to create for each instrument of seko: concept scheme:

Julkaisut

If the classification is translated to Finnish it can be published as a separate book including all the classes. Needs a publisher. The classification can be produced and published as a separate concept scheme. When used with the SEKO3 ontology, only those classes would be used where there are representatives in the SEKO concept scheme. This way the adding of classes/groups would be easier as the number of them would be lower. And we could still map to the narrower class concepts in the original MIMO service.

Updates to the classification