<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx</link><description>I've seen some signs of confusion about custom schema support lately. For example, I've seen a vendor claim that Open XML's support for custom schemas is "essentially inherent in XML itself" and that "there is nothing that OOXML supports via custom schemas</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>[OpenXML] Les schémas métiers expliqués ...</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2755578</link><pubDate>Mon, 21 May 2007 01:15:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2755578</guid><dc:creator>Blog de Neodante (Julien Chable)</dc:creator><description>&lt;p&gt;J'aurais aim&amp;#233; faire un post complet, &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx"&gt;http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Custom Schemas are the key for interoperability with your business data</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2770719</link><pubDate>Mon, 21 May 2007 20:16:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2770719</guid><dc:creator>Brian Jones: Open XML Formats</dc:creator><description>&lt;p&gt;Doug had a great post last week discussing the importance of custom defined schemas. Check it out: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.asp"&gt;http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.asp&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2790880</link><pubDate>Tue, 22 May 2007 14:42:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2790880</guid><dc:creator>Wu MingShi</dc:creator><description>&lt;p&gt;How is the example different from embedded XForm?&lt;/p&gt;</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2795439</link><pubDate>Tue, 22 May 2007 19:06:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2795439</guid><dc:creator>dmahugh</dc:creator><description>&lt;p&gt;I've not worked with XForms myself, but it's my understanding that the XForms output control is analagous to structured document tags.&lt;/p&gt;
&lt;p&gt;XForms and custom XML parts are solutions to different business problems. &amp;nbsp;XForms are about putting forms in web pages (or other XML documents), and custom XML parts are about putting arbitrary XML instances inside documents. &amp;nbsp;Those custom XML parts may be treated as form data or they may be used in other ways, depending on the needs of the user and the application.&lt;/p&gt;
</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2796265</link><pubDate>Tue, 22 May 2007 19:50:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2796265</guid><dc:creator>BrianJones</dc:creator><description>&lt;p&gt;Doug's right, this goes far beyond basic forms. It's about structuring your document semantically. You could of course just add some basic structures which would make it look more like a form, or you could structure the entire document.&lt;/p&gt;
&lt;p&gt;-Brian&lt;/p&gt;</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2815419</link><pubDate>Wed, 23 May 2007 15:53:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2815419</guid><dc:creator>Wu MingShi</dc:creator><description>&lt;p&gt;Dear Mahugh, Jones,&lt;/p&gt;
&lt;p&gt;That was a bait question. ;-)&lt;/p&gt;
&lt;p&gt;The answer, as I see can tell, is about whether some form of processing is needed to extract the data. With XForm, it looks like some form of processing will be needed to convert the XForm data into custom schema, while according to your description, one can get the custom schema directly.&lt;/p&gt;</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2972492</link><pubDate>Tue, 29 May 2007 20:50:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2972492</guid><dc:creator>BrianJones</dc:creator><description>&lt;p&gt;:-)&lt;/p&gt;
&lt;p&gt;Yes, that's correct. The custom schema is stored as a seperate part, so you don't need to do any additional processing. You can just program directly against that part, as it will contain all of your data.&lt;/p&gt;
&lt;p&gt;-Brian&lt;/p&gt;</description></item><item><title>re: Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#2989888</link><pubDate>Wed, 30 May 2007 19:21:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2989888</guid><dc:creator>Doug Johnson</dc:creator><description>&lt;p&gt;I'm looking to combine pretty much everything I've been learning here.&lt;/p&gt;
&lt;p&gt;I have the situation of needing to combine a data extract from within our application with a Word document that is customizable by our users.&lt;/p&gt;
&lt;p&gt;Data binding looked like the answer, but I find that while the compatibility tool allows users of Word 2003 and earlier to open and/or save OpenXML docs, it will not do the data binding. &amp;nbsp;And, while I can mandate one copy of Word 2007 to create the original documents, I cannot force them to upgrade ALL of their Word installs, and that is what will be called after creating the updated document.&lt;/p&gt;
&lt;p&gt;Databinding in Word 2000-2003 on opening an OpenXML document would be a preferred solution, but couldn't find a way to do that.&lt;/p&gt;
&lt;p&gt;Unless you have a better idea, my current thought is to include the schema (can be different at each location) in the base document that is used and let the user do in document markup with that schema.&lt;/p&gt;
&lt;p&gt;Is there a way to store the schema in the document and reference it so it will show up in the developers side panel without making the user go through that step? &amp;nbsp;I am thinking something to the effect of &amp;lt;w:attachedshema=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://mystuff.com/MyStuff&amp;quot;/&amp;gt;"&gt;http://mystuff.com/MyStuff&amp;quot;/&amp;gt;&lt;/a&gt; then referencing the internal xsd, but I am not seeing how that would be done.&lt;/p&gt;</description></item><item><title>Can't make it to Orlando? - you can still visit Virtual Tech Ed</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#3069810</link><pubDate>Mon, 04 Jun 2007 02:43:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3069810</guid><dc:creator>Notes2Self.net</dc:creator><description>&lt;p&gt;Here's the official TechEd 2007 site , and here's the link to Virtual Tech Ed . Bob Muglia kicks things&lt;/p&gt;
</description></item><item><title>Open XML links for 10-11-2007</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#5407589</link><pubDate>Fri, 12 Oct 2007 01:39:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5407589</guid><dc:creator>Doug Mahugh</dc:creator><description>&lt;p&gt;Andy Updegrove's &amp;quot;Meanwhile, Back in Minnesota: Your Chance to Help&amp;quot; provides information about how to&lt;/p&gt;
</description></item><item><title>Open XML Resources for Developers</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#8346740</link><pubDate>Tue, 01 Apr 2008 01:22:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8346740</guid><dc:creator>Doug Mahugh</dc:creator><description>&lt;p&gt;Like many people, I thought we'd know the official outcome of the DIS 29500 process today, but it looks&lt;/p&gt;
</description></item><item><title>Open XML Resources for Developers-----Doug Mahugh</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#8348272</link><pubDate>Tue, 01 Apr 2008 18:30:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8348272</guid><dc:creator>cnblogs.com</dc:creator><description>&lt;p&gt;Open XML Resources for Developers Published 31 March 08 03:20 PM Like many people, I thought we&amp;amp;#39;d&lt;/p&gt;
</description></item><item><title>Doug Mahugh : Custom schemas revisited</title><link>http://blogs.msdn.com/dmahugh/archive/2007/05/19/custom-schemas-revisited.aspx#8520361</link><pubDate>Tue, 20 May 2008 03:52:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8520361</guid><dc:creator>247Blogging</dc:creator><description>&lt;p&gt;I've seen some signs of confusion about custom schema support lately. For example, I've seen a vendor claim that Open XML's support for custom schemas is &amp;amp;quot;essentially inherent in XML itself&amp;amp;quot; and that &amp;amp;quot;there is nothing that OOXML supports&lt;/p&gt;
</description></item></channel></rss>