don't use domain-specific prop descriptions/names

[VladimirAlexiev]

https://semiceu.github.io/MLDCAT-AP/releases/1.0.0/rdf/mldcat-ap.ttl.

Don't use domain-specific prop descriptions/names, else you end up with silly stuff like this:

dct:title a owl:DatatypeProperty;
  rdfs:comment 
    "The label of the attribute."@en, 
    "The name assigned to the quality type."@en,
    "This property contains a name given to the Catalogue. This property can be repeated for parallel language versions of the name."@en,
    "This property contains a name given to the Data Service. This property can be repeated for parallel language versions of the name."@en,
    "This property contains a name given to the Dataset. This property can be repeated for parallel language versions of the name."@en,
    "This property contains a name given to the Distribution. This property can be repeated for parallel language versions of the description."@en;
  rdfs:label 
    "name"@en,
    "title"@en .

dct:identifier a owl:DatatypeProperty;
  rdfs:comment
    "An unambiguous identifier for the quality type."@en,
    "File identifier"@en,
    "Pointer to the did."@en,
    "This property contains the main identifier for the Dataset, e.g. the URI or other unique identifier in the context of the Catalogue."@en;
  rdfs:label
    "did"@en,
    "id"@en,
    "identifier"@en .

A title is a title, no matter to what resource you apply it to.

I appreciate that you collect prop names/descriptions from all places where a prop is used.
But then, these characteristics should be universal, not specific to the place where used.

If you need to make a distinction, you can use scopeNote, eg:

dct:identifier a owl:DatatypeProperty;
  skos:scopeNote "In oml:DataQualityList, we use Decentralized Identifiers (did)".
  rdfs:seeAlso <https://www.w3.org/TR/did-core/>.

[VladimirAlexiev]

This is especially silly:

dct:type a owl:ObjectProperty;
  vann:usageNote "The recommended controlled vocabulary is the <a href=\"./codelist/estimationprocedure-type.html\">Estimation Procedure type</a> code list."@en,
    "The recommended controlled vocabulary is the <a href=\"./codelist/feature-type.html\">Feature type</a> code list."@en,
    "The recommended controlled vocabulary is the <a href=\"./codelist/flowparameter-type.html\">Flow Parameter type</a> code list."@en,
    "The recommended controlled vocabulary is the <a href=\"./codelist/predictionfeature-type.html\">Prediction Feature type</a> code list."@en;
  rdfs:comment "A classification for a quality."@en, "A classification of the attribute."@en;
  rdfs:label "type"@en .

So... which is the recommended controlled vocabulary really?