wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] Groups - WEF substitutableMsg
- From: "Murray, Bryan P." <bryan.murray@hp.com>
- To: "Thomas Studwell" <studwell@us.ibm.com>,"Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- Date: Tue, 16 Nov 2004 15:06:44 -0800
I don't think you can prevent the use of xsi:type if a
client wants to use it. I also don't think we need to require it. In Tom's
example the type information is actually very useful. For instance the client
could also have sent the 2nd value as an int rather than base64 and still comply
with the requirements of the message. On the other hand, the first value will
always be interpreted as a string, so I don't think it is necessary to include
xsi:type.
If we are defining something around message catalogs we
need to be sure to say what happens when the substitution values can not be used
in the catalog message. For instance, what happens if the 2nd value sent in
Tom's example is 'hello world'?
Bryan
Yes, I like it. That's what I was looking for.
Re: William's comment
about the msgIdType (I'm now thinking msgIdCatalog would be a
better name) being a URI, I think I agree with this since it would permit
getting a catalog set if you don't have it handy. I do think that the values
must be typed so, even if you know what the message substitution requires,
having the types specified allows typesafe conversion. I think Igor's proposal
is a good way to address the problem. I'll check internally to see if anyone
sees a problem with URI.
Thomas W. Studwell
Senior Technical Staff
Member, Autonomic Computing Architecture
IBM Software Group
C151/Bldg
500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628
Mobile: (919) 619-1038
studwell@us.ibm.com
"What marks the mind of the
strategist is an intellectual elasticity or flexibility that enables him to come
up with realistic responses to changing conditions... In strategic thinking, one
first seeks a clear understanding of the particular character of each element of
a situation and then makes the fullest possible use of human brainpower to
restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind
of the Strategist)
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
11/16/2004 12:01 PM |
|
Then may be the right way of doing it in XML
is
<substitutableMsg msgId=”xs:string” msgIdType=”xs:string”?>
<value>xs:anyType</value>*
</substitutableMsg>
?
That way when
serialized properly it will be
<substitutableMsg msgId=”DBT1234E”
msgIdType=”IBM3.4”>
<value
xsi:type="xs:string">backup</value>
<value
xsi:type="xs:base64binary">0A120987BEA49342</value>
</substitutableMsg>
-- Igor Sedukhin
..
(igor.sedukhin@ca.com)
--
(631) 342-4325 .. 1
CA Plaza, Islandia, NY 11749
From: Thomas Studwell [mailto:studwell@us.ibm.com]
Sent: Tuesday,
November 16, 2004 11:05 AM
To: wsdm@lists.oasis-open.org
Subject: RE: [wsdm] Groups - WEF
substitutableMsg
Igor,
thanks for the comment. I wasn't clear on how
substitutableMsg was used. Let me try again with a possibly more correct
version.
Message catalogs exist for different languages so that messages
displayed on an English console can render the same information as a message
rendered on a French console by simply changing the Language catalog used. In my
example the msgIdType specifies
the base catalog, not the "type" of the data, and the local setting determines
which language version of the base catalog is used. Then the msgId of "DBT1234E" is used to pull out the text
from the catalog and, from the English catalog the following string is
returned:
"Database copy initiated, %s process, transaction ID:
%x."
This string has formatting information for two substitution values,
one string type, one hexadecimal formatting of an integer. Substituting, the
rendored message would read:
"Database copy initiated, backup process,
transaction ID: 0A120987BEA49342."
The French catalog would yield
something like:
"La copie de données a inauguré, procédé de backup,
transaction ID: 0A120987BEA49342."
In the doc I had mistakenly thought I
could simply type the values using type element names. Perhaps a better way is
to have the {any} element a named element with a type attribute. For
example:
<substitutableMsg msgId=”xs:string” msgIdType=”xs:string”?>
<value
valueType="xs:string">xs:any</value>*?
</substitutableMsg>
?
where valueType has enumerated values of
string, integer, hexadecimal, float so that the appropriate type conversion of
the values can be performed.
The example would now be
stated as:
<substitutableMsg msgId=”DBT1234E”
msgIdType=”IBM3.4”>
<value>”backup”</value> ! string could
be the default type
<value
valueType="hexadecimal">”0A120987BEA49342”</value>
</substitutableMsg>
Thomas W. Studwell
Senior Technical Staff Member, Autonomic
Computing Architecture
IBM Software Group
C151/Bldg 500
4205 S Miami
Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919)
619-1038
studwell@us.ibm.com
"What marks the mind of the strategist is
an intellectual elasticity or flexibility that enables him to come up with
realistic responses to changing conditions... In strategic thinking, one first
seeks a clear understanding of the particular character of each element of a
situation and then makes the fullest possible use of human brainpower to
restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind
of the Strategist)
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
"Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
11/15/2004 01:49 PM |
|
Should do
<substitutableMsg msgId="xs:string">
xs:anyType
</substitutableMsg> ?
E.g. instance of
this
<substiutableMsg msgId="abc"
xsi:type="java:ExceptionString">
<[[CDATA[ X.y.Z.Class threw exception
... ]]>
</substiutableMsg>
-- Igor Sedukhin ..
(igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749
-----Original Message-----
From: studwell@us.ibm.com
[mailto:studwell@us.ibm.com]
Sent: Monday, November 15, 2004 11:20 AM
To:
wsdm@lists.oasis-open.org
Subject: [wsdm] Groups - WSDM_EventFormatV0.7f.doc
uploaded
The document WSDM_EventFormatV0.7f.doc has been submitted by
Thomas
Studwell (studwell@us.ibm.com) to the OASIS Web Services
Distributed
Management (WSDM) TC document repository.
Document
Description:
[WEF] Updated doc includes new values for Severity based on
input from
Homayoun. Thanks Homayoun.
Download Document:
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/10094/WSD
M_EventFormatV0.7f.doc
View Document
Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=10094
PLEASE NOTE: If the above links do not work
for you, your email
application may be breaking the link into two pieces.
You may be able
to copy and paste the entire link address into the
address field of your
web browser.
To unsubscribe from this
mailing list (and be removed from the roster of
the OASIS TC), go
to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.
To unsubscribe from this mailing list (and be
removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]