In many of the examples we see that RDF Lists are used as the object of some property.
This is most of the time an error, and lead to wrong inferences.
For example if the range of aec3po:hasCheck is defined as aec3po:CheckStatement,
and a RDF graph contains [] aec3po:hasCheck ( <el1> <el2> <el3> )
Then the object of aec3po:hasCheck is actually an instance of rdf:List , which can be inferred to be a aec3po:CheckStatement
Then individuals <el1><el2><el3> are not check statements themselves.
It would probably better be modeled as [] aec3po:hasCheck <el1> , <el2> , <el3>.
In many of the examples we see that RDF Lists are used as the object of some property.
This is most of the time an error, and lead to wrong inferences.
For example if the range of aec3po:hasCheck is defined as aec3po:CheckStatement, and a RDF graph contains
[] aec3po:hasCheck ( <el1> <el2> <el3> )
Then the object of aec3po:hasCheck is actually an instance of rdf:List , which can be inferred to be a aec3po:CheckStatement Then individuals
<el1>
<el2>
<el3>
are not check statements themselves.It would probably better be modeled as
[] aec3po:hasCheck <el1> , <el2> , <el3>
.