Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: advice on xmlns requested

From: Bob Schloss <rschloss@--.---.--->
To: Ken_Gross@-----------.---, -------------@--.---
Date: 7/27/2004 7:17:00 AM




Hi Ken,

      It is best practice that have targetNamespace be an absolute URI,
something like
http://www.countrywide.com/xmlns/WebServiceModel
      and to have all namespaces specified also with an absolute URI,
something like
xmlns:AILoan="http://www.countrywide.com/xmlns/AILoan"

      This is not because we expect any schema processor at runtime to
deference a web document at that URI, but because there is likely to be
less confusion if all namespaces are fully specified, and not a function of
where any validating parser happens to run or be installed on your deployed
systems or in your development tools.  It will also simplify things if down
the road a schema is constructured to specify a legal document structure
that includes elements or types some of which came from your schema and
some of which came from someone elses schema -- you avoid the problem that
you both happened to use a general phrase such as WebServicesModel.  It
reduces the chances of the same name being used for two different sets of
schema components.

      For more information, see Namespaces in XML 1.1 [1] and/or Namespace
in XML [2].

            Good luck,
            Bob

Scalable XML Infrastructure - IBM Thomas J Watson Research Center -
Yorktown Heights, New York, USA
http://www.research.ibm.com/XML
http://www.research.ibm.com/people/s/bschloss

[1] http://www.w3.org/TR/2004/REC-xml-names11-20040204/
[2] http://www.w3.org/TR/1999/REC-xml-names-19990114/






                                                                           
             Ken_Gross@Country                                             
             wide.Com                                                      
             Sent by:                                                   To 
             xmlschema-dev-req         xmlschema-dev@w...                
             uest@w...                                                cc 
                                                                           
                                                                   Subject 
             07/26/2004 03:02          advice on xmlns requested           
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





Is the following  schema header valid?  If not, what would make it valid?

<xsd:schema targetNamespace="WebServiceModel"
elementFormDefault="unqualified"
attributeFormDefault="qualified"
xmlns:AILoan="AILoan"
xmlns:WebServiceClass="WebServiceClass"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:WebServiceModel="WebServiceModel">

Thanks

Ken

From Ken_Gross@C...  Tue Jul 27 11:56:13 2004
Return-Path: <Ken_Gross@C...>
X-Original


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent