* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #49 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Say that fragment identifiers are not scheme-specific

Reported by: duerst@it.aoyama.ac.jp Owned by: tony@att.com
Priority: major Milestone:
Component: 4395bis Version:
Severity: - Keywords:
Cc:

Description (last modified by ted.ietf@gmail.com) (diff)

From Björn Höhrmann, reported at http://lists.w3.org/Archives/Public/public-iri/2010Oct/0019.html:

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

comment:1 Changed 3 years ago by ted.ietf@gmail.com

  • Owner set to tony@att.com
  • Description modified (diff)

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 3 years ago by tony@att.com

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