v3 Support for RDFS without OWL

[jamrce]

trafficstars

pyLODE v2 supports ontologies that use rdfs:Class and owl:Class. However testing with v3 appears to only support owl:Class. Is this a choice that has been made with the development of pyLODE or just an issue from the current status of development?

Note: the pyLODE README about what it supports still states both. There is a typo there that support should be for rdfs:Class, not rdf:Class once this issue is clarified.

I've tested with both my own .ttl file ontology and also modifying the minimal example below with the same result - rdfs:Class entities not being generated in the documentation.

Modified minimal example

@prefix : <http://example.com/minimal/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://example.com/minimal>
    a owl:Ontology ;
    rdfs:label "Minimal Ontology" ;
    dct:created "2018-02-16"^^xsd:date ;
    rdfs:comment """This is a minimal ontology for testing pyLODE"""@en ;
.

:isProfileOf
    a rdf:Property ; # This works regardless of being an rdf:Property or owl:ObjectProperty
    rdfs:label "is profile of" ;
    skos:definition "A specification for which this Profile defines constraints, extensions, or which it uses in combination with other specifications, or provides guidance or explanation about its usage"@en ;
.

:Profile
    a rdfs:Class ; # This doesn't work for rdfs:Class but does for owl:Class
    rdfs:label "Profile" ;
    rdfs:subClassOf dct:Standard ;
    skos:definition """A specification that constrains, extends, combines, or provides guidance or explanation about the usage of other specifications."""@en ;
.