Open elf-pavlik opened 1 year ago
Please note that "mime type" and "MIME type" were never correct and should not be used in current or future works. "MIME" expands to "Multipurpose Internet Mail Extensions", and the Media Types used with MIME have many other applications (such as web architecture)
Please always use "Media Type" going forward.
Using http://www.w3.org/ns/ma-ont#format
seems a decent choice to me, even if the Media Ontology feels rather arbitrary in its choice of properties.
I would suggest using whatever predicate we decide on together with the W3C's RDF mapping of IANA Media Types (https://www.w3.org/ns/iana/media-types/), or the very similar endeavour by SPAR (http://www.sparontologies.net/mediatype/).
Generally agree that rdf:type
may be inadequate for what's intended but I'm not sure at the moment if it is wrong per se.
Minor comment requesting clarification:
Was http://www.w3.org/ns/ma-ont#hasFormat
intended instead of #format
? I see:
:hasFormat
a owl:ObjectProperty ;
rdfs:comment "Corresponds to 'format' in the Ontology for Media Resources." ;
rdfs:domain :MediaResource .
And I'm not sure if that seems appropriate either:
:MediaResource a owl:Class;
rdfs:comment "An image or an audiovisual media resource, which can be composed of one or more fragment / track.";
owl:disjointWith :Rating,
:TargetAudience .
or at least what's intended for #contained-resource-metadata
Did I misunderstand what's being sought in this issue?
This was mentioned during 2023-05-31CG meeting
4.2.1 Contained Resource Metadata states:
Advertising the mime type with
rdf:type
has a couple of issuesrdf:type
property can have any number of values, mime-type should have none for RDFSources and exactly one for Non-RDFSourcesIn sai-js I just picked an arbitrary
http://bblfish.net/work/atom-owl/2006-06-06/#type
. In CSS I see usage ofhttp://www.w3.org/ns/ma-ont#format
, which seems a better choicehttps://www.w3.org/TR/mediaont-10/#core-property-lists
For now, I'm going to align what sai-js uses with CSS (
http://www.w3.org/ns/ma-ont#format
). I think Solid Protocol should recommend this (or equivalent) predicate and use it in all relevant shapes.