You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why do you need new classes Dataset, Distribution, DataService? You can apply your props to existing classes. IMHO only DataProduct is needed.
If it's not the intent to create subclasses, then show the namespace for each class, and do something about the pink "subclass" arrows (maybe make them dashed and without arrowheads)
why add rdfs:label? dcat:Resource uses dct:title
More comments:
Maybe informationSensitivityClassification should be raised to Resource because Distributions might have different sensitivity?
dprod:Protocol claims to be "A detailed specification, possibly including a specific version, for how to communicate with a service." but has no properties. Either elaborate or delete this class
The text was updated successfully, but these errors were encountered:
@rivettp just to clarify/verify, we mean here that we want to show the prefix dcat: in front of class names like @VladimirAlexiev mentioned in his first bullet point right? Because we do not redefine those classes in OWL, they're just referred to from some shapes...
Comments based on the diagram in #94 (comment):
Dataset, Distribution, DataService
? You can apply your props to existing classes. IMHO onlyDataProduct
is needed.rdfs:label
?dcat:Resource
usesdct:title
More comments:
informationSensitivityClassification
should be raised toResource
becauseDistributions
might have different sensitivity?Range: dcat:SecuritySchemaType
. But there is no such class indcat
, change it todprod
dcat:Protocol
dprod:Protocol
claims to be "A detailed specification, possibly including a specific version, for how to communicate with a service." but has no properties. Either elaborate or delete this classThe text was updated successfully, but these errors were encountered: