Hi Harry,
Yes, your understanding below is correct. And after our
Montreal review, my intent at next revision is to drop the
'Any' from the '[Report|Alert|Action]ElementAny' definitions.
It confuses people and is odd naming.
As you note 'ReportElementAny' is single valued, so that
it can be used in a sequence of zero of more in the
'Report[Requested|Unsupported]Elements' definitions.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com
-----Original Message-----
From: owner-wims at pwg.org [mailto:owner-wims at pwg.org]On Behalf Of Harry Lewis
Sent: Tuesday, August 24, 2004 12:56 AM
To: wims at pwg.org
Subject: WIMS> ReportElementAny
I think I've asked for clarification before but, evidently, I have yet to
completely understand the verbal responses.
In report-20040622.xsd, what is the purpose of "ReportElementAny"
<xsd:element name="ReportElementAny">
<!-- OPTIONAL - MUST be single-valued -->
<!-- any element (and value) from any namespace -->
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReportElementAnyName" type="xsd:NMTOKEN"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReportElementAnyValue" type="xsd:anyType"
minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
why is it single valued, and how does it compare with "ReportElementAny"
inside "ReportRequestedElements"?
Is the above just the schema DEFINITION of a "ReportElementAny" (i.e.
name:value pairs) and the later is the schema for how to build the list of
elements returned in the report?
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------