Opened 9 years ago

Closed 8 years ago

#49 closed defect (fixed)

Say that fragment identifiers are not scheme-specific

Reported by: duerst@… Owned by: tony@…
Priority: major Milestone:
Component: 4395bis Version:
Severity: - Keywords:

Description (last modified by ted.ietf@…)

From Björn Höhrmann, reported at

As an unrelated point, a common confusion is that people think the fragment identifier is a scheme-specific, it's common for proposed registrations to define the fragment as part of the scheme, and it is unfortunately common that fragment identifiers are in fact treated as data, like "javascript:open('#example')" or "data:,#example" in implementations. However, fragment identifiers are part of the generic framework, the scheme-specific part ends where the fragment begins. I think 4395bis should discuss this problem in some detail.

Change History (2)

comment:1 Changed 8 years ago by ted.ietf@…

  • Description modified (diff)
  • Owner set to tony@…

The authors believe that the correct place to define the syntax is the base spec. A scheme definition cannot override the overall syntax for IRIs: this means # cannot be re-used outside the generic syntax restrictions and in particular this means that scheme-specific syntax cannot over-ride the fragment identifier syntax, since it is generic.

comment:2 Changed 8 years ago by tony@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.