What SKOS concepts should we use to structure the catalog?

[jeff-zucker]

The use of SKOS and SHACL together can be a potent way to structure the catalog in an easily discoverable fashion.

AFAIK, we can do things like this :

:StatusShape
    a sh:NodeShape;
    sh:targetSubjectsOf adms:status;
    sh:property [
        sh:path adms:status;
        sh:hasValue [
            a skos:Concept;
            skos:broader :SolidStatuses;
        ];
    ]
.
:SolidStatuses a skos:Concept; skos:inScheme :SolidCatalogTaxonomy.                                                                 
:Exploration a skos:Concept; skos:broader :SolidStatuses; skos:prefLabel "Exploration"@en .    
:Development a skos:Concept; skos:broader :SolidStatuses; skos:prefLabel "Development"@en .    
:Production  a skos:Concept; skos:broader :SolidStatuses; skos:prefLabel "Production"@en .     
:Archived a skos:Concept; skos:broader :SolidStatuses; skos:prefLabel "Archived"@en .                  

We can refer to existing SKOS schemes as appropriat.

More soon ...

[jeff-zucker]

A related issue for later examination - the possibility of linking skos:Concepts to rdfs:Classes. See the discussion at https://matrix.to/#/#linkeddata_chat:gitter.im/$uuzG2k9gSeT50W_ecHusdgMqe6CStTIRufsfrurP5Ro.