Turtle files difference PO and DoCO

[floresbakker]

I am using your SPAR ontologies a lot. I am using DoCO to model budgetary documents (“unanticipated reuse of ontology”) and I am quite satisfied with it. Great work you did! I did notice something that I do not quite follow.

https://sparontologies.github.io/doco/current/doco.ttl
https://sparontologies.github.io/po/current/po.ttl

From PO:

:containsAsHeader a owl:ObjectProperty ;
    rdfs:label "contains as header"@en ;
    rdfs:comment "A structured element contains another generic element as part of its header."@en ;
    rdfs:subPropertyOf :contains ;
    owl:inverseOf :isContainedByAsHeader .

:isContainedByAsHeader a owl:ObjectProperty ;
    rdfs:label "is contained by as header"@en ;
    rdfs:comment "An element is contained by another structured element as part of its header."@en ;
    rdfs:subPropertyOf :isContainedBy .

:contains a owl:ObjectProperty ;
    rdfs:label "contains"@en ;
    rdfs:comment "A structured element contains another generic element."@en ;
    rdfs:domain :Structured ;
    owl:inverseOf :isContainedBy .

From DoCO:

pattern:isContainedByAsHeader a owl:ObjectProperty .

pattern:contains a owl:ObjectProperty ;
    rdfs:subPropertyOf terms:hasPart .

Would you say that DoCO additionally defines the two mentioned object properties (through the IMPORT and then adding extra triples to define the objectproperty)? Wouldn’t this be against customs in modelling of ontologies by changing entities of original ontologies in other ontologies? And why does DoCO define pattern:contains with an additional rdfs:subPropertyOf terms:hasPart and not in the original PO? By defining the subproperty terms:hasPart the contains property becomes very powerful, so I was hoping to see it in the PO ontology. Additionally, it seems pattern:containsAsHeader is missing from DoCO?