Which part in OOXML SDK would be impacted by the I4I Verdict? Can someone explain in detail? RRS feed

All replies

  • From my understanding (and according to the press release below), they would have to remove the functionality to read CustomXml from future versions of Word including Word 2007 sold after January 11th.

    I would assume this means inline custom xml and custom xml parts and content controls but clarification is needed. I am also hoping it does not affect the OpenXml SDK as we use that heavily.


    Wednesday, December 23, 2009 4:17 PM
  • see this: http://milan.kupcevic.net/custom-xml-microsoft-office-word-data-store-i4i-patent-5787449-msdn/ ,but i am still not quite sure about the exact impact...

    it seems that ONLY Custom Xml Part has been "chopstuck" into the "hotpot"...

    obviously ,the inline Custom Xml Markup is utterly another thing.. (this is what i would like to make sure first)
    let alone that SDT has got nothing to do with this at all ,of course...

    waiting for official confirmation...
    Welcome to My Blog: xiaoyuvax.spaces.live.com | Follow me on Twitter: twitter.com/xiaoyuvax
    Wednesday, December 23, 2009 4:29 PM
  • Custom XML is one of the most powerful feature of Open XML specification. I hope MS is able to retain .. calling it by any name doesn't matter.
    MS may appeal against this judgement.



    Thursday, December 24, 2009 5:11 PM
  • Microsoft has added to the confusion by calling two completely different things by the name "custom XML." Here's a blog post that defines the difference and also shows which type of custom XML is affected by this patent case.


    The Custom XML part and Content Controls mapped to that custom XML are still in Word 2010 and are not impacted by this judgment. Embedded custom XML tags are going away.
    • Edited by CoderDennis Thursday, December 24, 2009 5:24 PM added hyperlink
    • Proposed as answer by CoderDennis Thursday, December 24, 2009 5:25 PM
    Thursday, December 24, 2009 5:23 PM
  • It seems really terrible for me...  i've to rewrite my program over again and it's just completed ...
    but custom XML markup is the most wonderful part in OOXML.... 

    Welcome to My Blog: xiaoyuvax.spaces.live.com | Follow me on Twitter: twitter.com/xiaoyuvax
    Friday, December 25, 2009 8:15 AM
  • Thursday, January 7, 2010 6:21 AM
  • The Open XML SDK is not affected by this decision.
    Zeyad Rajabi (MS)
    • Proposed as answer by Lu Zhang Monday, January 11, 2010 1:13 AM
    Friday, January 8, 2010 8:11 AM
  • your hint seems to be a good news....

    however Word 2010 beta does remove customXml markups produced by my program,as causes certain problems, while luckily my application still works well as long as Word is not involved...

    What exactly do you mean by "not affected", does it mean those classes supporting customXml markups would not be removed anyway,and just because the fact that  the OpenXml SDK is and has been always resumed a standalone implementation of OOXML standard rather than a SDK for development of Office? and the developers can still implement customxml markups in their solution ,even though Word does not support it at all??

    anyway,i've decided to implement a parellel sdt version of my solution,and i've looked into this transition problem, sdt and customXmlElement have similar architectures coming up with similiar properties as well,and i may suggest that perhaps a common base class for both sdt and customXml markup classes might help programmers to ease this transition or  implementation of a parallel solution,if they want a better compatiability with Word....

    Welcome to My Blog: xiaoyuvax.spaces.live.com | Follow me on Twitter: twitter.com/xiaoyuvax
    Monday, January 11, 2010 3:50 PM
  • What do you mean as STD and customXmlElement? Please can you post a link? I need to implement an alternative strategy. We have a development heavy based on this feature and now all we have done go away!!!!!!

    We have the same problem and it's incredible that Microsoft stop this very important feature for Word 2007 and over. It's incredible.

    I'm astonished !
    Thursday, February 18, 2010 1:59 PM
  • Check out Gray's blog for information on how on alternative solutions to custom xml markup: http://blogs.technet.com/gray_knowlton/

    To calrify my previous statement, Word will not write or read in custom xml markup after the patch. However, the file format and the Open XML SDK will still support custom xml markup. That being said, as mentioned above, any document with custom xml markup will have that markup stripped on open within a patched Word client application.
    Zeyad Rajabi (MS)
    Tuesday, February 23, 2010 3:23 AM
  • I need custom XML in the Word client! See other post forum: http://social.msdn.microsoft.com/Forums/en-US/oxmlsdk/thread/a871cfcd-ed39-4e08-8abb-28981d7ea850/?prof=required.

    Thanks a lot
    Tuesday, February 23, 2010 6:37 AM