- From: Rob Atkinson <rob@metalinkage.com.au>
- Date: Tue, 27 Sep 2016 16:05:40 +0000
- To: Andrea Perego <andrea.perego@jrc.ec.europa.eu>, Frans Knibbe <frans.knibbe@geodan.nl>
- Cc: SDW WG Public List <public-sdw-wg@w3.org>
- Message-ID: <CACfF9Ly=G-ugpYf8Wg9-E=9ZW+FuR_2448v7tNtmREozQvXeYA@mail.gmail.com>
IMHO fragment identifiers are for URLs not URIs :-) just redirect to a fragment for a given serialisation choice. On Wed, 28 Sep 2016 at 01:26 Andrea Perego <andrea.perego@jrc.ec.europa.eu> wrote: > I may have found a way to make frag ids work properly on github.io. > > We just have to use the full URL, including the file name: > > http://w3c.github.io/sdw/bp/index.html#describe-geometry > > Cheers, > > Andrea > > > On 27/07/2016 14:23, Frans Knibbe wrote: > > Thanks Andrea. I can confirm that the problem only seems to occur with > > github.io links. That is a relief, because that means the nuisance is > > only there for us, not for our public. > > > > Regards, > > Frans > > > > > > > > On 27 July 2016 at 14:16, Andrea Perego <andrea.perego@jrc.ec.europa.eu > > <mailto:andrea.perego@jrc.ec.europa.eu>> wrote: > > > > Same problem here. > > > > Not sure, but probably this is due to how github.io > > <http://github.io> renders HTML pages. When accessing specs in W3C > > space with the new layout, I don't have this issue. > > > > Andrea > > > > > > On 27/07/2016 13:40, Frans Knibbe wrote: > > > > Hi all, > > > > I notice that URIs with fragment identifiers, > > like http://w3c.github.io/sdw/bp/#describe-geometry don't work > > well in > > my browser (Chrome). I should land in Best Practice 10 (found > > that out > > by going to the HRML source code), but I wind up in the middle > > of BP 2. > > I have the feeling it has to do with the (new) layout for W3C > > documents, > > specifically the navigation sidebar. In Firefox I arrive at the > > right > > spot in the document, but if I pop out the sidebar and then open > > the URI > > in another tab, I land in a seemingly random position. > > > > I have noticed the same problem in the UCR document. Does anyone > > notice > > the same problem? If I am not the only one, we should probably > > try to > > fix the problem, because this does hamper readability of the > > deliverables. > > > > Regards, > > Frans > > > > > > > > -- > > Andrea Perego, Ph.D. > > Scientific / Technical Project Officer > > European Commission DG JRC > > Directorate B - Growth and Innovation > > Unit B6 - Digital Economy > > Via E. Fermi, 2749 - TP 262 > > 21027 Ispra VA, Italy > > > > https://ec.europa.eu/jrc/ > > > > > > -- > Andrea Perego, Ph.D. > Scientific / Technical Project Officer > European Commission DG JRC > Directorate B - Growth and Innovation > Unit B6 - Digital Economy > Via E. Fermi, 2749 - TP 262 > 21027 Ispra VA, Italy > > https://ec.europa.eu/jrc/ > > ---- > The views expressed are purely those of the writer and may > not in any circumstances be regarded as stating an official > position of the European Commission. > >
Received on Tuesday, 27 September 2016 16:06:28 UTC