<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sonja, i think it would be great if the VCI schema files belonged to a
WIDAR namespace.<br>
<br>
Namespaces<br>
1. ...help prevent naming collisions<br>
2. ...make the domain to which a particular type belongs more obvious<br>
<br>
All the SSS XML schema files (<a href="https://e2e.nrao.edu/schemas/">https://e2e.nrao.edu/schemas/</a>,
which also has some non-SSS files) are namespace qualified. The SSS
schema concerned with instrument configuration will refer directly to
VCI types (already begun, actually) -- we won't reinvent those types
over here. Using the "widar" prefix for those types makes the schema
files more readable.<br>
<br>
While my initial attempts to mix non-namespace-qualified VCI into the
SSS schemata have been successful so far, i think in the long run we'd
be better served by having a widar namespace.<br>
<br>
Amplifying on your example, here's what a phony type definition in an
SSS schema file would look like with namespace qualified elements:<br>
<blockquote><tt><xs:schema<br>
version = "1.0"<br>
xmlns:xs = <a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema"><font color="red"><b>MailScanner has detected a possible fraud attempt from "www.w3.org" claiming to be</b></font> "http://www.w3.org/2001/XMLSchema"</a><br>
targetNamespace = <a class="moz-txt-link-rfc2396E" href="http://www.nrao.edu/namespaces/sss">"http://www.nrao.edu/namespaces/sss"</a><br>
xmlns:sss = <a class="moz-txt-link-rfc2396E" href="http://www.nrao.edu/namespaces/sss">"http://www.nrao.edu/namespaces/sss"</a><br>
xmlns:widar = "some-URI-defined-by-Sonja"<br>
elementFormDefault = "qualified"><br>
...<br>
<xs:complexType name="fooBar"><br>
<xs:element name="nowFor" type="xs:double"/><br>
<xs:element name="something" type="sss:frequency"/><br>
<xs:element name="completelyDifferent"
type="widar:AntennaType"/><br>
</xs:complexType><br>
...<br>
</xs:schema><br>
</tt></blockquote>
<br>
Barry wrote:<br>
<blockquote type="cite">
<pre wrap="">What does JAXB do with this?</pre>
</blockquote>
Well, JAXB supports namespaces, so we can at least rest easy that
putting elements into a namespace won't cause troubles w/ JAXB. Other
than that, the choice to use namespaces not really tied to the choice
of technology used to create and consume the msgs. <br>
<br>
David<br>
</body>
</html>