wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] MUWS Comments part 2
- From: "Vambenepe, William N" <vbp@hp.com>
- To: "Zhili Zhang" <zhili@tibco.com>,"Heather Kreger" <kreger@us.ibm.com>
- Date: Wed, 1 Dec 2004 19:13:01 -0800
(1) is fixed
The namespace prefix, unless it is
xml
or
xmlns
, must have been declared
in a namespace declaration attribute in either the start-tag of the
element where the prefix is used or in an an ancestor element (i.e. an element
in whose content the prefixed markup occurs). The prefix
xml
is by definition bound to
the namespace name http://www.w3.org/XML/1998/namespace
. The prefix xmlns
is used only for namespace bindings and is not itself
bound to any namespace name.
I have
seen many long discussions about whether it is required, advised,
unrecommendable or illegal to explicilty declare this namespace. I don't know
what the concensus is on best approach. It is now in the
schema.
On
(3), I added wstop and wsa. wsrf-rp is only used in the schema (with a prefix
definition) not in the text or the examples so we don't need to define it in the
table.
On
(4) I'd much rather not make the spec any longer than it needs to be. So let's
not put this in the schemas in appendix since the one already in the doc
presumably covers the whole doc. We might want to put the disclaimer in the
"Standalone" schema documents when we post them though.
Thanks,
William
Hi
William,
Here
are my comments on document
wd-wsdm-muws-part2-1.0-20041126.doc.
muws-p2-xs:DescriptionProperties
muws-p2-xs:MetricsProperties
muws-p2-xs:RelationshipsProperties
muws-p2-xs:RelationshipResourceProperties
(2)
QName "xml:lang" is used in schema. Strictly speaking, the XSD should have the
following import statement:
Other
validators like .NET may work well with it. However, a simple fix like this
will make WSDM schemas solid.
(3)
The namespace table in Introduction section (page 5) lists namespaces for
ServiceGroup (wssg), etc. Couple of others are missing from the table, such as
wsrf-rp, wstop, wsa.
(4)
Should we insert OASIS legal disclaimer into normative XSDs, WSDLs, topic
instances? Schemas and WSDLs from other groups like WSN, WSRF have
it.
Thanks
Zhili
Here are my comments on
MUWS Part 2.
My biggest
issues are:
1. In Platform
Properties - addresses addressing more that properties, split out into two
sections and make more normative references to resource properties specs.
2. Need Topics in the events section.
3. Configuration is missing half its
section
4. Advertising is missing
advertisement by registration
Heather Kreger
STSM, Web Services Lead Architect for SWG
Emerging Technologies
Author of "Java and JMX: Building Manageable
Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441)
cell:919-496-9572
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]