Quotes about xml (16 Quotes)


    Even though Office 12's adoption of XML might cause pain in the near term, it is an architectural necessity for moving forward, ... It will be hard to convince people to go back and figure out every macro already in their company and find an alternative means of doing the same thing. But in the long run, having this as a separate engine is going to be more appropriate and more scalable down the line.


    I want to write XML and have XML in my business applications. To their credit WAP is opening e-business for low bandwidth devices, but moving forward it is a different story.

    The whole business-to-business game of developing the right infrastructure will continue to play out. There will be key decisions around XML Extensible Markup Language or a competing technology relating to b-to-b information transfer.

    The ODF Alliance (Sun, IBM and their friends) apparently want to push ODF as an 'exclusive' standard to the detriment of all others vs. enabling choice among formats such as PDF from Adobe, Open XML, HTML and others.


    What should we do to bring Office's classic COM-based publish-and-subscribe capabilities to a world where RSS and XML have become the de facto publish-and-subscribe mechanisms ... Connected Office.

    There are a lot of different implementations out there at the moment. A common extension for XML will benefit enterprises because they'll be able to count on this API to be stable and secure, and they needn't be concerned about incompatibilities with each vendor using a proprietary parser.

    In the last six months, we've seen a sharp increase in both the demand for Berkeley DB XML and the volume of XML data under management. Any developer that needs to store XML data can benefit from Berkeley DB XML. If the developer is suffering from performance problems with their XML-based application, they absolutely should download and use our new version of Berkeley DB XML today.

    Developers won't need to build these classes themselves, and XML documents won't be as bulky as they might be because we won't need to include these classes in the application code.

    It's a chicken or the egg principal. Carriers and brokers are asking 'who is going to adopt this first. 'Who is going to be the leader to build an ACORD XML interface' The risk is the first one out there is going to have to find a partner to do it with to try to get some type of ROI.



    The kind of programming that C provides will probably remain similar absolutely or slowly decline in usage, but relatively, JavaScript or its variants, or XML, will continue to become more central.

    The proposed policy is inconsistent with ongoing dialogues Microsoft is having with other Massachusetts state agencies about how Microsoft products can best meet their data and records requirements for a variety of data types - ranging from traditional documents to pictures, audio, video, voice, voice-over-IP, data, database schema, web pages, and XML information. As we look to the future, and all of these data types become increasingly intertwined, locked-in formats like OpenDocument are not well suited to address these varying data types - as the proposed policy itself acknowledges. It's this need for choice and flexibility that led Microsoft to design Office in a way that supports any XML schemas that a customer chooses, a capability lacking in less functional formats.

    In the customer care space there are a lot of systems that store data -- CRM, trouble ticketing, order entry, order management. This data needs to be pulled out and made accessible to the customer care agent. We come into play where we are about seamlessly encapsulating the back-end systems and making that xml data available to front-end applications. It automates business processes moving away from manual.

    Microsoft is ahead of the market in facilitating rich and simplified integration of XML and other verbose meta-language capabilities into all of its products, ... As such, storage and management of new, verbose data remains at the center of the integrated Windows story guided by DSI.



Authors (by First Name)

A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z

Other Inspiring Sections