Re: Comments on "Locators for Web Publications"

Reflecting on one technical issue:

<snip>
> 
>> The discussions we had about fragment ids om WP resolved around using the existing fragids for the media types in use in the publications, such as HTML [3].  If  you disagree with this, please comment on the issue, but we did discuss it at length.
> 
> That issue (#27) only mentions fragments _once_ and I’m not even sure whether it meant fragment ids in that context. A fragment identifier is a separate topic from identifier, locator, or address for web publications. Identifying a resource is an entirely different issue from using a fragment identifier to identify a part of that resource.
> 
> My argument is that we only have a remit to define a fragment identifier that identifies a part of the document returned (not other linked resources) when you fetch the web publication (or manifest) URL, provided that the file returned is a new media type.
> 
> If fetching the web publication URL returns an HTML file as has been discussed[1], then defining a fragment identifier for the web publication URL in any way shape or form is outside of our remit. Defining fragment IDs for HTML files is, realistically, only going to be done by the WHATWG. Defining a fragment identifier for web publication URLs is not compatible with the idea of having those URLs return an HTML file.

That is a fair technical point: I must admit I did not realize the contradiction between the fragid as defined in the locator spec and the separate discussion on 'what should I get back when dereferencing the WP address'. If the latter defines (as it does) the the return is HTML, then the current definition is indeed wrong.

The fragid in the locator document has always been a topic of discussion, and we were never sure that we should do that in the first place (as witnessed by the open issue). Thanks for pointing this error out.

I am happy removing the corresponding section from the document even before FPWD, although it would help if that specific technical point was added, crisply, to the issue as a comment.

Thanks

Ivan

----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704

Received on Wednesday, 13 December 2017 08:51:04 UTC