Skip to main content

Home/ Document Wars/ Group items tagged blog

Rss Feed Group items tagged

Jesper Lund Stocholm

Microsoft Office 2010 Engineering : Open XML: One Year In - 1 views

  • What is noteworthy about this investment is that we’re working closely with members of JTC 1 SC 34 ( the standards body responsible with Open XML maintenance ) to identify and resolve backward compatibility issues related to this new functionality.
    • Jesper Lund Stocholm
       
      I think it is worth noting, that quite a few of the independant experts of WG4 have argued against usage of ISO-dates in T.
Gary Edwards

An interesting offer: get paid to contribute to Wikipedia - Rick Jelliffe - 1 views

  •  
    Classic argument about ODF vs OOXML.  Need to send Rick an explanation about how the da Vinci plug-in works.  It is entirely possible to capture everythign MSOffice editors do in ODF using namespace extensions compliant with ODF 1.1 standard.   What was impossible was to round-trip those MSOffice ODF documents to OpenOffice.org.  And as it turns out, replacing MSOffice/Windows on new workgroup desktops with OpenOffice/Linux was one of the primary objectives behind the Massachussetts effort to standardize on ODF.  They believed the hype that ODF was cross platform interoperable.  It wasn't then, and it still isn't five years later. As for capturing all the complexities and nuances of the very robust MSOffice productivity environment and authoring system?  Sure, ODf could easily be extended for that. What an incredible discussion!
Gary Edwards

Official Google Blog: Pagination comes to Google Docs - 0 views

  •  
    Although you need Chrome for the new Google Docs pagination feature, the key here is that gDocs now supports the CSS3 pagination module!   excerpt: Today, we're doing another first for web browsers by adding a classic word processing feature-pagination, the ability to see visual pages on your screen. We're also using pagination and some of Chrome's capabilities to improve how printing works in Google Docs. Native Printing: Pagination also changes what's possible with printing in modern browsers. We've worked closely with the Chrome team to implement a recent web standard, CSS3, so we can support a feature called native printing. Before, if you wanted to print your document we'd need to first convert it into a PDF, which you would then need to open and print yourself. With native printing, you can print directly from your browser and the printed document will always exactly match what you see on your screen.
Gary Edwards

Dump the file server: Why we moved to the SharePoint Online cloud [review] - 0 views

  • For this article, I wanted to focus on an important aspect of our move to Office 365, and that was our adoption of SharePoint Online as our sole document file server. I know, how passé for me to call it a file server as it represents everything that fixes what plagues traditional file servers and NASes. Let's face it: file servers have been a necessary evil, not a nicety that have enabled collaboration and seamless access to data. They offer superior security and storage space, but this comes at the price of external access and coauthoring functionality. Corporate IT departments have had a band-aid known as VPN for some time now, but it falls short of being the panacea vendors like Cisco make it out to be. I know this well -- I support these kinds of VPNs day to day. Their licensing is convoluted, they're drowning in client application bug hell, and most of all, bound by the performance bottlenecks on either the client or server end.
  • I previously wrote about how my company used to juggle two distinct file storage systems. We had Google Drive as our web-based cloud document platform, buts its penetration didn't go much further than its Google Docs functionality. That's because Google has a love-hate relationship with any Office file that's not a Google Doc. Sure, you can upload it and store it on the service, but the bells and whistles end there. Want to edit it with others? It MUST be converted to Google's format. And so we had to keep a crutch in place for everything else that had to stay in traditional Office formats, either due to customer requirements, complex formatting, or other reasons. That other device for us was a simple QNAP NAS box with 1.5TB of space.
  • I previously wrote about how my company used to juggle two distinct file storage systems. We had Google Drive as our web-based cloud document platform, buts its penetration didn't go much further than its Google Docs functionality. That's because Google has a love-hate relationship with any Office file that's not a Google Doc. Sure, you can upload it and store it on the service, but the bells and whistles end there. Want to edit it with others? It MUST be converted to Google's format.
  • ...9 more annotations...
  • And so we had to keep a crutch in place for everything else that had to stay in traditional Office formats, either due to customer requirements, complex formatting, or other reasons. That other device for us was a simple QNAP NAS box with 1.5TB of space.
  • We liked Google Drive's real time collaboration functionality, but the way it treated non-Docs files was pretty pitiful.
  • Dropbox for Business provides the best headroom for growth, but it's starting monthly price is too much to swallow.
  • And Box and Egnyte don't bring much more to the table besides bona fide cloud storage and sync;
  • SharePoint Online offers a rich ecosystem that we can grow on.
  • For the purpose of running our day to day business needs, SharePoint Online has taken over for both Google Drive and our former NAS alike. We don't have to convert items to and from Google Docs anymore just to collaborate. We have as good, or better, permissions in SharePoint compared to Google Drive. And the search power in SharePoint is disgustingly accurate, providing the accuracy and file previews that we were used to on Google Drive.
  • SharePoint Online is first and foremost a cloud solution that has additional tie-ins with Office Online products, OneDrive, etc that may or may not exist in the on-premise version of the product.
  • It's a cloud file server (the focus of this piece). It's a content search hub. It can run public websites and internal intranets. It can help handle complex document workflows. You can even run Access databases on it.
  • I can finally work as I wish, in-browser or in Office 2013 -- or both at once. My entire company "file server" is synced via OneDrive for Business to my Thinkpad, and likewise, I can edit any files in a browser via Office Online apps. It's a nirvana that Google Drive almost afforded us, if it weren't for Google's distaste of traditional Office files. It's good to know you can have your cake and eat it too.
  •  
    Yesterday Google announced dramatic price reductions for their Cloud Computing platform. This announcement was followed immediately by a similar announcement from Amazon. But what about Microsoft? The truth is that Microsoft doesn't need to reduce prices, and they are forcing both Google and Amazon reductions. My guess is that there are more reductions to come too. The answer is in this review of SharePoint OnLine and Office 365, where the author points out the fact that Google Drive / Apps totally mangles an MSOffice document. Once Google converts the documents, they are useless. "I previously wrote about how my company used to juggle two distinct file storage systems. We had Google Drive as our web-based cloud document platform, buts its penetration didn't go much further than its Google Docs functionality. That's because Google has a love-hate relationship with any Office file that's not a Google Doc. Sure, you can upload it and store it on the service, but the bells and whistles end there. Want to edit it with others? It MUST be converted to Google's format. And so we had to keep a crutch in place for everything else that had to stay in traditional Office formats, either due to customer requirements, complex formatting, or other reasons. That other device for us was a simple QNAP NAS box with 1.5TB of space." In 2006-2007, when we were in the middle of the great ODF vs OOXML document wars, I had a conversation with Google's Open Source - Opoen Standards guru, Chris DiBona. It was during the Massachusetts crisis, and we were trying to garner Google Corporate support for ODF. Chris listened to my pitch and summarized his position that conversion methods were very advanced, and going forward, file formats really didn't matter. He famously said, "Let a thousand formats bloom". I wonder if he still thinks that?
Gary Edwards

Just how much bigger AWS is compared its next competitor may surprise you | Network World - 0 views

  • For reference, Microsoft's latest quarterly earnings statement does not break out revenue for Azure specifically, and it breaks up revenue for its different cloud products into different commercial and licensing categories. One of those categories, the commercial division had cloud services revenue that doubled in the quarter, growing $367 million, mainly from Office 365 commercial sales.
  • Brandon Butler — Senior Writer Senior Writer Brandon Butler covers the cloud computing industry for Network World by focusing on the advancements of major players in the industry, tracking end user deployments and keeping tabs on the hottest new startups. He contributes to NetworkWorld.com and is the author of the Cloud Chronicles blog
  • Email him at bbutler@nww.com
  •  
    "Amazon.com came out with its quarterly earnings last week and Technology Business Research analyst Jillian Mirandi crunched the numbers of how much of a lead AWS has on its competitors in the public cloud market. The numbers are striking. AWS broke $1.1 billion in quarterly revenues for cloud IaaS in the first quarter of 2014. The company's next closest competitor in the cloud IaaS market, IBM, came in at $350 million. That's almost a three-fold lead for AWS compared to the nearest competitor, according to TBR. Behind IBM, Microsoft and Google close out the top four public cloud IaaS providers, but those latter two companies only generated about $30 million in cloud IaaS revenue last quarter, TBR estimates."
Gary Edwards

ODF - the state of play - The future of ODF under OASIS, now that the... - 1 views

  •  
    "ODF - open document format - is an open, XML-based rich document format that has been adopted as the standard for exchanging information in documents (spreadsheets, charts, presentations and word processing documents), by many governments and other organisations (see, for example, here), including the UK Government. This is despite strong opposition by Microsoft; but I have seen Microsoft's proposed "open XML" standard and, frankly, it is huge and horrid (in the word of standards, these go together). If I remember correctly, the early draft I saw even incorporated recognition of early Excel leap-year bugs into the standard. ODF is now a pukka ISO standard, maintained by OASIS, under the proud banner: "The future is interoperability". My personal thoughts, below, are prompted by an ODF session at ApacheCon Core titled "Beyond OpenOffice: The State of the ODF Ecosystem" held by Louis Suárez-Potts (community strategist for Age of Peers, his own consultancy, and the Community Manager for OpenOffice.org, from 2000 to 2011), and attended by very few delegates - perhaps a sign of current level of interest in ODF within the Apache community. Nevertheless, and I am talking about the ODF standard here, not Apache Open Office (which is currently my office software of choice) or its Libre Office fork (which seems to be where the excitement, such as it is, is, for now), the standards battle, or one battle, has been won; we have a useful Open Document Format, standardised by a recognised and mature standards organisation, and even Microsoft Office supports it. That's good. So what could be the problem? Well, I don't care whether I use ODF from Open Office, Libre Office or even Office 365, I just want to be sure that everyone else can read my ODF documents (with a .odt, .ods or .odp extension, for text, presentation or spreadsheet, respectively), with whatever software they like; and that they'll either see exactly the functionality and formatting I see; or a well defined (an
Gary Edwards

Microsoft pushes Trade Secrets Bill - 1 views

  • A spokesman for the Microsoft On The Issues website has expressed the company’s support for new legislation that would reform the legal framework for companies wishing to protect their trade secrets in a cloud-centric world where such information is frequently forced to reside on networks. In the post Microsoft’s Assistant General Counsel of IP Policy & Strategy Jule Sigall rallies behind business and academic concerns supporting the proposed Defend Trade Secrets Act 2015 (DTSA), which goes before the United States Senate Judiciary Committee today. Sigall, who is also Associate General Counsel for Copyright in Microsoft’s Legal & Corporate Affairs department, makes an ardent case for reform of the current legislation, as furnished by the Uniform Trade Secrets Act (UTSA). UTSA’s provisions are argued to be fractured, and rendered ineffective both by the inability of plaintiffs to pursue suits in federal courts (despite trade secret infractions being Federal by nature), and by the fact that not all states have adopted or instituted all the measures provided by the legislation. Additionally the limited provision for redress in international cases of trade secret theft are to be addressed.
  • Sigall presents the case of Microsoft’s Cortana AI as an example of why new legislation is necessary: ‘[Behind] Cortana sits a vast amount of technology developed or enhanced in-house by Microsoft – voice recognition; language translation; reactive and predictive algorithms that can synthesize context, location and data, and interface with the vast resources of the Bing search engine index; and a complex array of cloud servers to crunch and serve data in real time. This technology represents tens of thousands of hours of research, trial and error, and continued improvement as Cortana is adapted for new devices and new scenarios’
  • Sigall argues that better protection procedures for trade secrets, the only form of IP which currently lacks comprehensive cover in law, is essential for start-ups whose ideas, business plans and even customer lists may constitute the only marketable value of a company that is just in the stage of consolidating. ‘A trade secret is unique among forms of intellectual property in how it is legally protected. While it is a federal crime to steal a trade secret, a business that has its trade secrets stolen must rely on state law to pursue a civil remedy. Owners of copyrights, patents, and trademarks can go to federal court to protect their property and seek damages when their property has been infringed, but trade secret owners do not have access to such a federal remedy.’
  • ...7 more annotations...
  • Defend Trade Secrets Act 2015 contains [PDF] significant material from its doomed predecessor of 12 months ago, and one of its boldest initiatives is the extension of ex parte seizures, instituted in UTSA in a more limited form (particularly in the 1985 amendment to the Uniform Law Commission’s 1979 initial legislation). An ex parte seizure provides a kind of restraining order or injunction on disputed information, or even the dissemination of knowledge about whether the information is disputed, and places it under federal protection on the plaintiff’s behalf.
  • Microsoft had a hard time adjusting to the open source revolution, particularly in regard to the PC/Mac Office product which at one time represented the most successful and ubiquitous software in the world, and the many legal and semantic wrangles over the closed-source nature of Office formats such as Word led ultimately to a hybridised open source .docx format which is still argued to not be the OpenXML that was promised.
  • According to Sigall the state-by-state system currently in place was ‘simply not built with the digital world in mind’, and calls for ‘A uniform, national standard for protection’ which does not stop at state lines or even national borders.
  • In practical terms this seems likely to extend the circumstances under which information about leaks, hacks or thefts of information can be made the subject of gag orders for legal reasons, since it brings trade secrets into the same legal framework as other forms of intellectual property which enjoy more comprehensive coverage and recourse in law. The bill would also extend the purview of the 1996 Economic Espionage Act to take in a more rigorously conceived concept of ‘trade secrets’.
  • Even with the issues clear, the risk of disproportionate or over-reaching response in the event of the new bill passing successfully through congress in 2016 (it is unlikely to pass this year) is clear enough that the lack of network discussion about it is quite surprising. Essentially DTSA represents the same kind of proposed ‘judicial fast track’ – though in favour of corporations instead of governments – that has outraged so many commenters in the wake of the November 13th Paris attacks.
  • Silence in court Amongst its more quotidian clauses, the Defend Trade Secrets Act 2015 effectively offers corporate plaintiffs increased opportunity to federalise disputed private material in cases involving trade secrets, with all the penalties for infraction associated with that change of status – and far greater scope for sub judice orders likely to contain and conceal future breaches of information.
  • Eric Goldman of the Santa Clara University School of Law has just published a paper outlining the risks of extending ex parte seizures in the manner that DTSA 2015 proposes. Goldman writes that ‘the Seizure Provision does not solve many, if any, problems. In light of the remedies already available to trade secret owners in ex parte temporary restraining orders (TROs), the Seizure Provision purports to apply to only a narrow set of additional circumstances. In exchange for that modest benefit, the Seizure Provision creates the risk of anti-competitive seizures and seizures that cause substantial collateral damage to innocent third parties. To discourage such abuses, the Act imposes procedural safeguards and creates a cause of action for wrongful seizures. Unfortunately, those safeguards are miscalibrated to achieve the desired protections against abusive seizures.’
  •  
    Lots of possible Constitutional issues lurking. The Constitution creates only two types of intellectual property, patents and copyrights. "(P)roperty interests . . . are not created by the Constitution. Rather, they are created and their dimensions are defined by existing rules or understandings that stem from an independent source such as state law." Ruckelshaus v. Monsanto Co., 467 US 986 (1984), https://goo.gl/ZljO1H (trade secrets case). The traditional source of rights in trade secrets have been state law. Thus there is a state's rights issue lurking in this legislation, a question whether the federal government is invading the States' police power, an "our federalism" question.
« First ‹ Previous 141 - 147 of 147
Showing 20 items per page