There are special Properties that are predified Classes in RDF, which are first cases of defining Classes and Property Hierarchy,
rdfs:SubPropertyOf which are transitive Property to define inheritance hierarchies for Classes and Properties.
If one defines a new Property on has to define a Domain from a Class which is mapped to another Class that is the Range. So the there Properties to define an RDFS Domain and Range. These are two Properties that maps the property to its Domain and Ranger
This Terminology Knowledge is expressed by Classes and the Relation between these Classes and is the Ontology or the Terminology part of the RDFS Knowledge Base.
Defining Conceptional Models is pretty simple in RDF Schema. The RDF part is the Instantiation of this RDFS Termonological Knowledge
rdfs:subClassOfTransitive Property to define Inheritance Hierarchies for Classes
rdfs:subProbertyOfTransitive Property to define inheritance Hierarchies for Properties
rdfs:domaindefines the Domain of a Property concerning a Class
rdfs:rangedefines Range of a Property concerning a Class
Further Properties like
rdfs:seeAlso are for looking up Information that explains a Resource. In a formal way a Dubproperty of
rdfs:isDefinedBy that defines the Relation of Resource and its Definition. If one only need to make a Comment on something, which is not a Definition, one can use the Property rdfs:comment. In general it is agreed on that if one names Resources one usually takes the Property
rdfs:label there is always be a for a human and machine readable name of a Resource, which is contrary to an ID which is only a alphanumeric String that does not be human readable. So the real name of a Resource has to be readable.
rdfs:seeAlsodefines a Relation of a Resource to another, which explains it
rdfs:isDefinedBySubproperties of rdf:seeAlso, defines the Relation of a Resource to its Definition
rdfs:commentComment, usually as Text
rdfs:label"readable" name of a Resource (contrary to ID)