clarify inputBytes, inputDocument, inputMediaType

[TallTed]

fixes #1402

---

Preview | Diff

[iherman]

A very practical issue aiming to avoid future merge conflicts...

Following the WG agreement, I have created a PR (#1440) changing the property mediaType to encodingFormat. I was wondering whether it wouldn't be better, for the sake of consistency, to use the term inputEncodingFormat instead of inputMediaType in this algorithm. It may be wiser if we agreed on this issue in this PR and, possibly, the term was changed here (and my PR concentrates exclusively on the property).

Note that the term mediaType also appears in the body of the algorithm. That should either be changed or kept unchanged, in sync with the change of the argument name.

Personally, I am in favour of changing the algorithm argument name, but I won't lie down the road if the agreement is to leave it as is.

[TallTed]

Consistency is generally better than not.

That said, I don't like the change to encodingFormat because I don't think it's an accurate label nor particularly well defined by schema.org.

I also note (too late for that decision, but perhaps it might be reconsidered) https://www.w3.org/ns/iana/media-types/ which seems like it should be taken into account for W3 purposes.

[iherman]

Consistency is generally better than not.

That said, I don't like the change to encodingFormat because I don't think it's an accurate label nor particularly well defined by schema.org.

I have to agree with you on this. As I said, I can live with inconsistency; we just to agree that we all accept it.

I also note (too late for that decision, but perhaps it might be reconsidered) https://www.w3.org/ns/iana/media-types/ which seems like it should be taken into account for W3 purposes.

This is a very strange namespace (never saw this before). It seems to assign, for each specific media type, a class. If we used this, Example 28 would look like:

  "image": {
     "id": "https:....",
     "digestSRI" : "sha384-......",
     "type" : "https://www.w3.org/ns/iana/media-types/image/svg+xml#Resource"

this can work, but I am afraid it would be a bit unnatural to use...

@msporny @dlongley ?

[TallTed]

s/"https://www.w3.org/ns/iana/media-types/application/svg+xml#Resource"/"https://www.w3.org/ns/iana/media-types/image/svg+xml#Resource"/, I think?

(And, of course, the document at the latter link includes mention of application/svg+xml which is not listed in the main table on https://www.w3.org/ns/iana/media-types/. sighs)

[iherman]

s/"https://www.w3.org/ns/iana/media-types/application/svg+xml#Resource"/"https://www.w3.org/ns/iana/media-types/image/svg+xml#Resource"/, I think?

Yep, sorry. I will edit the comment just to make it o.k.

(And, of course, the document at the latter link includes mention of application/svg+xml which is not listed in the main table on https://www.w3.org/ns/iana/media-types/. sighs)

[decentralgabe]

@iherman this one ready too?

[iherman]

@decentralgabe yes. The issue of mediaType remaining is still pending, the other PR has been closed, so it should not affect this PR. Merge ahead...

[decentralgabe]

editorial approval, open >1 week, changes addressed. merging!