solid / solid/specification

Recommend predicate for a literal media type (Content-Type)

Open
#537 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
563
Forks
108
Avg merge
4d 13h
Merged PRs (30d)
3

Description

This was mentioned during 2023-05-31CG meeting

4.2.1 Contained Resource Metadata states:

rdf:type
A class whose URI is the expansion of the URI Template [RFC6570] http://www.w3.org/ns/iana/media-types/{+iana-media-type}#Resource, where iana-media-type corresponds to a value from the IANA Media Types [IANA-MEDIA-TYPES].

Advertising the mime type with rdf:type has a couple of issues

  • rdf:type property can have any number of values, mime-type should have none for RDFSources and exactly one for Non-RDFSources
  • providing it as IRI requires the use of the IRI Template to compare it with the literal value of the registered media type

In sai-js I just picked an arbitrary http://bblfish.net/work/atom-owl/2006-06-06/#type.
In CSS I see usage of http://www.w3.org/ns/ma-ont#format, which seems a better choice

https://www.w3.org/TR/mediaont-10/#core-property-lists

format
The MIME type of the resource (e.g., wrapper or bucket media types, container types), ideally including as much information as possible about the resource such as media type parameters, for example, using the "codecs" parameter [RFC 4281].

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read section 4.2.1, the linked 2023-05-31 meeting notes, and the Media Ontology format property discussion. Compare the current Solid Protocol wording with sai-js and the relevant shapes; done means the predicate choice and its use across all relevant shapes are agreed and reflected in the specification.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.