w3c / wpub

W3C Web Publications
https://w3c.github.io/wpub/
Other
78 stars 19 forks source link

update links description to try and better clarify uses #301

Closed mattgarrish closed 6 years ago

mattgarrish commented 6 years ago

Let me know if this makes things any better (or worse). I separated out the "linked to" use cases from the "resources not to be taken offline or packaged" to try and make it less confusing.


Preview | Diff

llemeurfr commented 6 years ago

This makes things really clearer. Only the last part is still fuzzy IMO:

User agents MAY ignore linked resources, and are not required to take them offline with a Web Publication. These resources SHOULD NOT be included when packaging a Web Publication.

... means that the author cannot expect that links will survive offlining and packaging. This is consistent with the description of what links are.

The completeness of the links list might affect the usability of the Web Publication in certain scenarios (e.g., if a user agent does not take them offline). For this reason, it is strongly RECOMMENDED to provide a comprehensive list of all of the Web Publication's non-critical resources.

... could mean many obscure things. What is the connection between completeness of the list of links and offline reading? (if a link is not present, it's not present online and offline). Why is this sentence useful? I would remove it.

... could mean that authors can expect that

mattgarrish commented 6 years ago

... means that the author cannot expect that links will survive offlining and packaging.

I'm not seeing that. It refers to the resources being optional to take offline or package. We don't say to scrub the infoset when going offline, or not to include the manifest in the package, so there should always be persistence that way.

Why is this sentence useful? I would remove it.

It was copied over from the resource list -- where it also makes more sense if you fail to list resource that are needed offline. At this point, given how we're stressing non-essential for links, it does seem a bit contradictory. I'm not sure the lack of a font will seriously affect usability. Were there other cases you had in mind @iherman, or do you think it can be dropped?

llemeurfr commented 6 years ago

@mattgarrish my bad, I didn't mean that the link would disappear when offlining the content, but that the referenced content will not be fetched, therefore will not be accessible offline. Forget it.

iherman commented 6 years ago

@mattgarrish yes, this seems to be copied from resources, and I agree it can be removed.

mattgarrish commented 6 years ago

Any thoughts on this before merging, @dauwhe?