CR ISSUE: DOM interface needs module

• From: John Boyer <JBoyer@PureEdge.com>
• Date: Mon, 10 Feb 2003 13:44:15 -0800
• To: <www-forms-editor@w3.org>
• Cc: <w3c-forms@w3.org>
• Message-ID: <7874BFCCD289A645B5CE3935769F0B52452A16@tigger.pureedge.com>

The IDL description of XFormsModelElement must belong to a module.
 
For example, in the load & save spec:
 
http://www.w3.org/TR/2002/WD-DOM-Level-3-LS-20020725/
 
They define the module as:
 
#pragma prefix "dom.w3c.org"
module ls
{
    interface DocumentLS : Document{
             attribute boolean         async;
     };
};
 
Note: The module is fully defined as dom.w3c.org.ls
 
We need something like:
 
#pragma prefix "w3c.org"
module xforms
{
   interface XFormsModelElement : Element {
     org::w3c::dom::Document               getInstanceDocument(in org::w3c::dom::DOMString instance-id)
                                                raises(org::w3c::dom::DOMException);
     void                   rebuild();
     void                   recalculate();
     void                   revalidate();
     void                   refresh();
   };
};
 
NOTE: Fully qualified names are used for Document, DOMString and DOMException since xforms is not in their module space.

John Boyer, Ph.D.
Senior Product Architect
PureEdge Solutions Inc.

Received on Monday, 10 February 2003 16:44:46 UTC