 |
 |
 |
James Delmonico asks:
>> I am curious why the specification defines that this information must be
declared again locally when in my case it is being declared by the
imported
schema?
Sam Ruby was kind enough to post in his blog the slides for a talk I gave
on XML schema a few years ago. If you can handle powerpoint, take a look
(sorry, no HTML or PDF at the moment.) See [1,2]. I suggest you run
them in full slide show mode to see the animations properly (press F5 if
you're in powerpoint or just run in the browser if in IE) and go through
to the group starting with slide 25 that's titled "Our language vs. your
langugae - why <import>?" , Some of the other slides may be if interest
to readers of this list too. I hope this helps.
Noah
[1] http://www.intertwingly.net/blog/906.html (blog entry)
[2] http://intertwingly.net/slides/2002/devcon/SchemaSecrets.ppt (slides)
--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
From nobody@w... Wed Jun 23 12:56:02 2004
Return-Path
|
 | 



|  |
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.
|  |
| |
 |
 |
 |