15926.org

1.

<owl:ObjectProperty rdf:about="#hasObjectRoleFiller">
<rdfs:label>hasObjectRoleFiller</rdfs:label>
</owl:ObjectProperty>

Should not domain be declared: TemplateStatement?


2.

<owl:Class rdf:about="#RDLTemplate">
<rdfs:label>CoreTemplate</rdfs:label>

Should be <rdfs:label>RDL Template</rdfs:label>.

3. <owl:Class rdf:about="#RDLTemplateStatement">
<rdfs:label>RDLTemplateStatement</rdfs:label>
<rdfs:subClassOf rdf:resource="#BaseTemplateStatement"/>

Why RDLTemplateStatement is subclass of BaseTemplateStatement?

On 1) and 2)
I think it's better to wait on the new template model you guys are developing.

On 3)
I don't know what the meaning is of an RDLTemplateStatement
Location (the RDL) has nothing to do with models.
Location is about namespaces and even then it can be having another endpoint address than namespace address.

If I would guess, the RDLTemplateStatement is a synonym for SpecializedTemplateStatement.
As I can see from here, the SpecializedTemplate exists in the upcoming new template model, but there are no more "Statement" classes.
See for the current discussion this publication

Onno,

Again, new model is far ahead in my opinion. If 2 is a mistake, probable it'll be better to correct it. You'll be issuing a new versions once new namespaces are approved, it'll be a good opportunity.

When new p7tm ontology will be ready, it'll be necessary to preserve backward compatibility and keep "Statement" classes mapped to there equivalent classes in new model.