title: Modelling RDF item features as subclasses or as references to other individuals
body: <p>I'm wondering what are the implications (i.e., benefits and drawbacks) of modelling RDF item features as:</p>
  
  <ol>
  <li>classes (i.e., individuals belonging to a subclass)</li>
  <li>individuals referring to another abstract individual representing a feature.</li>
  </ol>
  
  <p>I don't want to use data properties. I need to represent clear concepts with their IRIs.</p>
  
  <p><strong>Example type 1</strong></p>
  
  <pre><code>@prefix : &lt;http://example.org#&gt; .
  
  :Car a rdfs:Class .
  :Subaru rdfs:subClassOf :Car .
  :Mercedes rdfs:subClassOf :Car .
  :Ferrari rdfs:subClassOf :Car .
  
  :c1 a :Subaru .
  :c1 a :Mercedes .
  :c1 a :Ferrari .
  </code></pre>
  
  <p><strong>Example type 2</strong></p>
  
  <pre><code>@prefix : &lt;http://example.org#&gt; .
  
  :Car a rdfs:Class .
  :CarModel a rdfs:Class .
  
  :Subaru a :CarModel .
  :Mercedes a :CarModel .
  :Ferrari a :CarModel .
  
  :c1 a :Car ;
      :model :Subaru .
  :c2 a :Car ;
      :model :Mercedes .
  :c3 a :Car ;
      :model :Ferrari .
  </code></pre>
  
  <p>Excuse me if this question could sound too broad. I'm aware there is any silver bullet in those cases and I'm trying to understand what are the implications of such different modelling strategies.</p>