Category: Content creation and design(Page 44 of 66)
Technologies and strategies for authoring and editing, including word processors, structured editors, web and page layout and formatting, content conversion and migration, multichannel content, structured and unstructured data integration, and metadata creation.
GIGXR, Inc., a provider of extended reality (XR) learning systems for instructor-led teaching and training, announced the availability of its GIG Immersive Learning System for the Fall 2020 Northern Hemisphere academic year. The cloud-based System was created to enhance learning outcomes while simplifying complex, real-life teaching and training scenarios in medical and nursing schools, higher education, healthcare and hospitals. The GIG Immersive Learning System is available for demos and pre-order now, and includes three core components:
Remote and Socially Distanced Learning: Enables teaching and training with students in a distributed classroom through extended reality. Students can be co-located, remote or safely socially distanced, and participate in sessions anywhere using 3D mixed reality immersive devices and mobile phones, tablets or laptops for a 2.5D experience.
Mixed Reality Applications: GIGXR’s products HoloPatient and HoloHuman run on Microsoft’s HoloLens 2, placing the 3D digital world in a collaborative physical space for safe development of clinical skills and exploration into human pathologies and anatomies.
Immersive Learning Platform: Cloud-based infrastructure that supports GIGXR’s mixed reality applications and remote learning capabilities with additional features such as visual login, instructor content creation, holographic content management, session planning, roles and rights, license management, security, privacy, and long-term data management.
Grammarly released a new feature exclusively for Grammarly Business customers: customizable company style guides. With a company style guide, Grammarly Business can deliver customized, real-time writing suggestions to employees and be confident that customers exploring the company blog, browsing your website, or chatting with your support team, they’ll always feel like they’re interacting with the same company. Training employees to write consistently in the company style requires a large — and ongoing — time investment. On top of that, employees may be writing in dozens of different interfaces and tools. Trying to ensure compliance with a manual review process is rarely scalable or sustainable. Over time, individual deviations from company style add up, creating confusion for customers, eroding trust, and negatively impacting your brand and bottom line.
Web development architecture based on client-side JavaScript, APIs, and markup.
The Jamstack is not about specific technologies. It’s a new way of building websites and apps that delivers better performance, higher security, lower cost of scaling, and a better developer experience. Pre-rendered sites can be enhanced with JavaScript and the growing capabilities of browsers and services available via APIs.
IXIASOFT, a DITA CCMS software company, and Precision Content, a provider of structured authoring and content management expertise announce partnership to help customers with the required support to identify, understand, and effectively address their content challenges. IXIASOFT’s newly formed alliance with Precision Content creates new capabilities to benefit from microcontent structures by linking a standardized content authoring methodology with the IXIASOFT CCMS software. Precision Content’s team of technical communication professionals focuses on reengineering how content is authored to help businesses implement innovative, scalable, and sustainable solutions to plan, author, and publish high-value content.
NetDocuments, the secure multi-tenant cloud-based content services and productivity platform for law firms, corporate legal teams, and compliance departments, announced the availability of ChatLink, an integration that links Microsoft Teams to NetDocuments. With ChatLink, Teams users now connect channels with NetDocuments workspaces and secure threads. ChatLink enables users to continue working inside the Microsoft Teams interface while maintaining complete access to NetDocuments workspaces and conversations within ndThread to adhere to compliance and governance rules. Administrators can manually or programmatically associate a channel with an existing NetDocuments matter or project, making documents available in a tab within the channel. Likewise, an embedded view of associated chats in ndThread, allow for multiple conversations to happen within a matter while securing them to the matter file.
EditShare’s new Flow panel for Adobe Premiere Pro is designed to simplify content management, proxy and remote editing, and review and approval workflows for editors. For open storage, EditShare’s EFS enhances collaborative editing with support for project-locking for Productions in Premiere Pro. With the Productions feature set, Premiere Pro can now handle projects with “an extraordinary number of assets” while maintaining peak performance. Sharing and organizing those assets is also simplified. Flow manages the entire media technology stack with tools to orchestrate assets and workflows across tiered on-premise, nearline and cloud storage environments. A secure platform for remote, collaborative productions, Flow offers an advanced proxy-based workflow with support for more than 500 codecs. Its enhanced Premiere Pro panel connects individual editors and production teams directly to the Flow media asset management and its productivity-focused toolset including extensive asset tracking, collaborative proxy editing workflow, and review and approval workflows across cities, countries and continents. EFS scalable storage enables media organizations to build extensive collaborative workflows on premise, in the cloud, or in hybrid installations, shielding creative personnel from the underlying technical complexity while equipping administrators and technicians with storage management tools. For Adobe editors, EFS is fast and flexible collaborative storage that supports Productions in Premiere Pro for project sharing.
An article on The Verge and quotes from Microsoft’s Jared Spataro about Fluid reminded Thompson of OpenDoc and he begins his own thoughts on Fluid with a bit of history on Steve Jobs decision to kill OpenDoc in 1997. Thompson suggests the reason was that a combination of Microsoft’s dominant marketshare, and
that the application model was simply a much better approach for the personal computer era. Given the lack of computing power and lack of connectivity, it made much more sense to have compatible documents made by common applications than to try and create common documents with compatible components — at least with the level of complexity implicit in OpenDoc.
Thanks to Thompson for giving me an excuse to indulge in a little history of my own, which largely supports his view. Below is what I shared with him. The history is fun, but the new Fluid Framework is also worth a closer look.
———————-
Fluid also reminded me of the competing OpenDoc and OLE approaches in the early 90s. To supplement your history…
At the first Documation conference in February 2004 1994 I moderated a session that included Apple Chief Scientist Larry Tesler, and Tony Williams, Microsoft Software Architect and Co-creator of COM. I had asked each of them to discuss requirements for and their approaches to building a “compound document architecture”. OpenDoc was naturally appealing to me (and many of my subscribers) at the time, but Tony made a strong case for OLE. Tony’s argument for OLE was technical but he also addressed the issue from a business point of view, and argued that OpenDoc was too much of a radical change for both developers and end users. While this was more of an issue for Microsoft with their large developer community and installed base, OpenDoc was radical, and I expect that was the reason OpenDoc languished at Apple and for Jobs’ ultimate rejection.
On Wednesday the general session was divided into two sections. One covered new technologies being developed to enhance document computing and document management. The other presented senior managers from large corporations who described their own document management needs.
Your editor opened the technology session by describing three components of current document management systems, each of which presage future developments. Objects — whether in terms of object-oriented databases, object-oriented programming, or multimedia document component “information objects” — play a big role in making systems more flexible and capable of dealing with complexity. Building an architecture to manage and share distributed objects, and to link and assemble them into document form are requirements of many enterprise-wide document management solutions. Finally, the document metaphor is increasingly seen as the most effective and friendly way to interface not only with document management systems, but with information in general.
Today, these capabilities are built either at the application level, or as “middleware”. For many reasons (e.g., application interoperability, performance, and ease of application development), it would help instead to have support for these capabilities at the operating environment level.
Previous attempts at compound document architectures to provide such an environment have failed. But this is clearly something we need, and eventually will get. Whoever defines and builds such an architecture will be in a powerful position to dominate the IT market. We can expect fierce battles among the platform and architecture vendors to control this architecture . The two leading candidates today are Microsoft’s OLE, and the Component Integration Lab consortium’s OpenDoc (based on Apple technology).
Larry Tessler from Apple described the “Information Tidal Wave” (his alternative to “superhighway”) coming with the growth of electronic multimedia documents, and with the rapid building of electronic document repositories. IS managers will face severe new problems arising from the need to manage these repositories. Larry positioned OpenDoc as a core technology for supporting the management and assembly of these new kinds of documents.
Microsoft’s Tony Williams focused on user requirements for a compound document architecture. Compound documents should be thought of as “compound views” of information, and documents are just one form of information, and thus need to be handled as part of an information architecture. Information architectures in turn need to be able to manage many different types of multimedia data for both document and data applications.
A standard “containment model” is needed, Williams said, to allow applications to share and organize information objects. Previous attempts at standard compound document architectures, e.g., ODA (Office, or Open Document Architecture) failed because they attempted to define a too restrictive representation. Such systems also need to handle ad hoc information (for example, that created with a personal information manager) as well as structured documents.
Tony emphasized the need to protect both user investments in information and developer investments in applications. While a compound document architecture environment is a requirement of any new operating environment, there must be an evolutionary path provided — a compound document architecture that forces a radical change too quickly will not gain acceptance. Tony positioned OLE as the technology that meets these requirements.
When asked, both Tony and Larry Tessler claimed that OpenDoc and OLE should work together and described generally — each in terms of the architecture they were promoting — how that could happen. However, this is definitely an area where there needs to be continued and aggressive vigilance on the part of corporate users to ensure that operating environment interoperability results. It would certainly not be wise — at least not yet — to assume that one of these approaches will become dominant.
Mathematical Markup Language (MathML) is an application of XML for describing mathematical notations and capturing both its structure and content. It aims at integrating mathematical formulae into World Wide Web pages and other documents. It is a recommendation of the W3C math working group. MathML is not intended to be written or edited directly by humans, but exceptions are more likely to be made for Presentation MathML than for Content MathML.
