[Bug 21887] New: [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions despite NAMESPACE being redundant

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21887

            Bug ID: 21887
           Summary: [Custom]: Add a note about using TYPE and NAMESPACE to
                    identify definitions despite NAMESPACE being redundant
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dominicc@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 1 May 2013 03:49:12 UTC