This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21887 - [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions despite NAMESPACE being redundant
Summary: [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions d...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency tree / graph
 
Reported: 2013-05-01 03:49 UTC by Dominic Cooney
Modified: 2013-05-21 22:19 UTC (History)
0 users

See Also:

Attachments

Description Dominic Cooney 2013-05-01 03:49:11 UTC 
The steps for register say "If there already exists a definition with the same TYPE, throw a NotSupportedError and stop." This means that TYPE uniquely specifies a definition.

However when referring to definitions, the spec usually (always?) refers to them by TYPE and NAMESPACE. For example, this from parsing:

"Let ELEMENT be the result of creating a node implementing the interface appropriate for the element type corresponding to TYPE and NAMESPACE"

I agree that this "TYPE and NAMESPACE" is a convenient way to sneak in a namespace check without complicating steps with explicit exits for mismatched namespaces. However it would be nice if there was non-normative language pointing out that the spec does this and there is this implicit namespace checking going on all over the place, which when it fails, is the same as a definition not being available.
Comment 1 Dimitri Glazkov 2013-05-21 22:19:07 UTC 
I think I'd rather just make this checks explicit: https://dvcs.w3.org/hg/webcomponents/rev/e96be051a09a