@prefix relations: <https://w3id.org/zpid/vocabs/relations/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

relations:
  skos:prefLabel "Resource Relations"@en, "Ressourcenbeziehungen"@de ;
  a skos:ConceptScheme .

relations:hasAnalyticCode
  rdfs:domain <http://id.loc.gov/ontologies/bibframe/Work> ;
  rdfs:range <http://id.loc.gov/ontologies/bibframe/Work> ;
  rdfs:subPropertyOf <http://id.loc.gov/ontologies/bibframe/supplement> ;
  skos:relatedMatch <https://osf.io/vocab/2022/hasAnalyticCodeResource>, <http://data.loterre.fr/ark:/67375/TSO-MBZXLNPD-1> ;
  skos:editorialNote "At crossref and datacite, both types - data and code from a study are related via 'is-supplemented-by'/'isSupplementedBy' to the article, with no differentiation between the two. At OSF, code is a resource attached to a registration, with a resource_type 'analytic_code', while data is resource_type 'data'."@en ;
  skos:broader relations:hasSupplement ;
  skos:scopeNote "Relates a work that is a research paper to computer code that was used to analyze the study's research data."@en ;
  skos:notation "Research Data 002" ;
  skos:inScheme relations: ;
  skos:prefLabel "has analytic code"@en, "hat Auswertungscode"@de ;
  a rdf:Property, skos:Concept .

relations:isAnalyticCodeFor owl:inverseOf relations:hasAnalyticCode .
relations:hasSupplement
  skos:prefLabel "has supplement"@en, "hat Supplement"@de ;
  a rdf:Property, skos:Concept ;
  skos:narrower relations:hasAnalyticCode .

relations:PSYNDEXresearchDataRelations
  skos:prefLabel "Werk zu Forschungsdatentypen"@de, "Work to Research Data Types"@en ;
  a skos:Collection ;
  skos:member relations:hasAnalyticCode .

