Thanks Gary,
Please wait until Tuesday. I will make the changes to the
Document of Record in the meeting, or in the evening after the
meeting. Just FYI Mr. Kumar's first name is Ram, e.g. Ram Kumar,
he is located in Australia, and I assume that is why he uses sydney in
hs address.
See you Tuesday.
Thanks again,
Rex
At 1:12 PM -0500 1/6/08, Gary Ham wrote:
Rex,
I have completed repairing the Example messages for
the specification such that they validate to CIQ 3.0!!! (Each must be
replaced.)
Subject to 2 caveats:
1.Resolution of the GML-CIQ
conflict on the use of the xlink namespace.
2.The possible error in the xAL
specification as defined below.
I believe that minor changes, if any, to the example
will be required. Unfortunately not all of them will fully
validate until the issues are resolved.
Do you want them now, or better I should wait until
Tuesday.
R/s
Gary A. Ham
http://grandpaham.com
703-899-6241
Grandpa can do IT!
From: Gary Ham [mailto:hamgva@cox.net]
Sent: Sunday, January 06, 2008 11:29 AM
To: kumar.sydney@gmail.com; sukumar_Dwarkanath@sra.com;
emergency-msg@lists.oasis-open.org; Tom Merkle
Subject: [emergency-msg] CIQ Issues
Sydney,
I am trying
to convert some Resource Messaging examples to CIQ 3.0 for our
Resource Messaging Specification.
It was
working well. I figured out most of the differences and was
making some progress when I suddenly got
unexpected
"Object
Reference not set to an instance of an object" and Unhandled
"System.NullReferenceException in XML Editor" errors in MS Studio
2005.
It occurred
when changing element names from xal:Name to xal:NameElement for
either xalAdministrativeArea or xal:Locality.
Interestingly, it does not happen when changing xal:Name to
xal:NameElement for xal:Country.
Weird??
Not trusting
the expensive Microsoft product, I returned to my free-ware X-Ray from
Architag International.
It detected
what it believes to be an error in the xAL schema. The following
is the text of the error message:
Invalid
content type by extension, <simpleContent> extension is not
allowed by <complexContent> Base Type:
'{urn:oasis:name:ciq:xal:3 }NameType' Derived
Type.
Schema Error
Location /schema{1}/complexType[position()=1 @name=
'AddressType']/sequence[1]/element[position() = 4 @name =
"Locality"/complexType[1]/sequence[1]/element[position0 = 1 @name =
['NameElement']/complexType[1]/complexContent[1]/extension[1]
Perhaps that
is why Visual studio is choking. It is certainly in the
same place (xal:Locality NameElement) Are you able to validate the
authenticity of the error?
As a matter
of interest, I may be involved with another use for CIQ besides
emergency messaging, if I can figure out how to make it work
consistently. The Commonwealth of Virginia, here in the US, is
looking at improving is Customer Record Management and I see a
potential match.
Gary A.
Ham
http://grandpaham.com
703-899-6241
Grandpa can
do IT!
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670