Employee Training Software Market
Permanent link to this press release:
Delete press release Edit press release
All 5 Releases

source

Signing out of account, Standby…
For many companies, critical data is locked on a printed page, stored in a box or sitting on someone’s desk. It isn’t easy to get that information flowing without scores of people to rekey it into an electronic format. These outdated practices are driving the adoption of intelligent document management.
Data is the lifeblood of any organization. When it flows freely, businesses can grow, win new customers and prepare for the future. When it’s constrained, stagnation sets in. Time and money are wasted, and emerging opportunities are missed.
For too many companies, critical data is locked on a printed page, stored in a box or sitting on someone’s desk who is out of the office. It’s difficult to get that information flowing without scores of people to rekey it into an electronic format so that it can be more easily shared, analyzed, processed and acted upon.
These outdated practices are driving the adoption of intelligent document management.
Document management has been around for a while. It generally refers to scanning all the pieces of paper in an office to understand what a company has so it can decide what to keep and develop a system of indexing that enables other employees to retrieve information.
Previously, companies manually indexed documents, meaning a human would look at a piece of paper, hone in on the vendor name and the account number, and key it into a database. Advancements then used optical character recognition (OCR) to aid in indexing. That is when software tries to figure out what each character is, for example, a machine reading six digits in an invoice and coming up with the number 123456. The trouble is that a “6” also looks like a “b,” so OCR is not highly accurate.
Traditional document management falls short in an important way: Information is only useful when inserted into workflows. This is where intelligent document management comes into play, and it’s critical to digital transformation.
Related: Finding the Right Solution for Your Bookkeeping Needs
Intelligent document management is more than a better way to scan documents because it enables information management. Thanks to its “intelligence,” intelligent document management offers automated classification, routing, measurement, monitoring and multi-channel information management fueled by artificial intelligence (AI).
Auto-classification means that scanners deploy AI to make intelligent decisions about what a page contains (e.g., recognize a bill of lading vs. an invoice) and categorize it.
Next, following the company’s internal workflows, it routes the electronic version of the document to the correct person based on a combination of roles and rules (e.g., Mary, the Comptroller, must approve all invoices over $10,000, while invoices less than $5,000 go to Fred). Approvals can co-occur or follow a strict, sequential order.
Monitoring is essential. What if Mary is away on vacation for two weeks, and that invoice must be paid? An intelligent document management tool has timers, recognizing when a deadline is approaching and notifying and rerouting the document to a designated person so it can be handled. It also monitors the overall process and reports it to management.
Finally, intelligent document management supports multi-channel information — whether a piece of paper from a vendor or a bill of lading generated from an order management system. AI ensures data is gleaned correctly and routed through the proper workflows.
With intelligent document management, roughly 90% of a document’s processing is handled by computer — decreasing administrative time, eliminating human error and saving money.
We believe the first step for intelligent document management is to fully document the current workflow by someone with information-management experience, not just IT experience. This is called a Business Process Analysis (BPA), and a solid grasp of how business is conducted is essential. Additionally, having experience rolling out future enterprise content management (ECM) initiatives within a Finance Department, HR Department, etc., is crucial if you want the final result to be a tenable solution that does what you need.
Then you need to decide what to digitize. Most organizations store more documents than they need. This scenario can lead to unnecessary risk, given emerging privacy laws and requirements protecting specific information types.
A document audit is required before digitization even starts. For instance, is a document, such as an employee contract, within its retention requirements, or are you no longer needed to keep it? If the latter, it’s probably better to destroy that document. Another consideration: Every page scanned costs money, so an audit will drive cost efficiency.
Next, you’ll need to develop a content roadmap for filing documents so that current and future employees can easily retrieve information. You have a photo of the Statue of Liberty. How should it be classified as a statue, national icon, New York City tourist attraction or gift from France?
You want to choose a vendor that works with you to guarantee successful outcomes and eliminates the risk of you making the wrong technology investments. Too often, companies underestimate the level of effort and complexity of a do-it-yourself (DIY) approach.
Many capture systems offer similar capabilities, but your experience with them may be highly influenced by the vendor. Is the vendor willing to do the critical document audit for you? Is the vendor willing to do the painstaking work of documenting your workflows so that the system lives up to its true potential? Does the vendor offer Service Level Agreements (SLAs), enabling you to hold the company accountable?
Getting the right solution at the right cost is key in any consideration. Intelligent document management providers charge money for an up-front analysis that highly trained, certified experts perform. A monthly subscription fee follows this to use the platform and a customization fee to implement your specific requirements. If you want to add more files to the system, there are fees to scan, extract and index those.
Related: This Startup Is Disrupting Decentralized Data Storage Industry
If the analysis is performed properly, you will know what it costs you now, where your bottlenecks are, where your risks and efficiencies are and what it will cost to improve. The BPA provides a quantitative pay-back period that allows you to make a heads-up decision based on facts.
Converting to an intelligent document management system will deliver immediate returns on investment and pay dividends well into the future. Mapping all incoming information to your unique workflows so that it can be processed with the minimal manual intervention will do more than save you time and money, however. It will ensure your company has the agility it needs to thrive in a fast-paced economy.
This Army Veteran Started Buying Rental Properties While on Duty and Is Now a Full-Time Real Estate Investor. Here Are His Top Tips for Success.
Having a Work-Life Balance Is Nonsense. To Reach Your Goals, Follow Another Approach.
Feeling Stuck? 5 Ways to Clear Your Mind and Be Your Most Productive Self.
These Founders Couldn’t Find Comic Books With Strong Black Characters, So They Created Them. Then Kevin Hart and Mark Cuban Invested $500,000 in Their Business.
Franchise Brands Need to Start Utilizing Video Marketing
What’s Your Listening Style? Knowing It Will Make You a Better Leader.
‘So, Tell Me About Yourself’: Use This 4-Step Formula to Answer This Dreaded Question
Emily Rella
Nitin Kumar
Emily Rella
Subscribe to our Newsletter
The latest news, articles, and resources sent to your inbox.
I understand that the data I am submitting will be used to provide me with the above-described products and/or services and communications in connection therewith.
Read our privacy policy for more information.
Copyright © 2022 Entrepreneur Media, Inc. All rights reserved.

Entrepreneur® and its related marks are registered trademarks of Entrepreneur Media Inc.
Successfully copied link

source

Hi, what are you looking for?
By
Published

New Jersey, N.J., July 21, 2022 The HR Document Management Software Market research report provides all the information related to the industry. It gives the outlook of the market by giving authentic data to its client which helps to make essential decisions. It gives an overview of the market which includes its definition, applications and developments, and manufacturing technology. This HR Document Management Software market research report tracks all the recent developments and innovations in the market. It gives the data regarding the obstacles while establishing the business and guides to overcome the upcoming challenges and obstacles.
Human resources document management software is used to store and protect all your documents associated with an employee, from hiring to retirement, in a centralized employee file.
Get the PDF Sample Copy (Including FULL TOC, Graphs, and Tables) of this report @:
https://www.a2zmarketresearch.com/sample-request/654644
Competitive landscape:
This HR Document Management Software research report throws light on the major market players thriving in the market; it tracks their business strategies, financial status, and upcoming products.
Some of the Top companies Influencing this Market include:PeopleDoc, SAP, eFileCabinet, Breathe, ServiceNow, DocuVantage, Zoho, Iron Mountain, Document Logistix, M-Files, Zenefits, Ceridian, Document Locator, Cleardata, DynaFile, Personio, Prosource, Natural HR, Access Group, myhrtoolkit, MaxxVault, Margolis, Biel, Hyland (OnBase), Crown Records Management, AODocs, DocStar, SearchExpress
Market Scenario:
Firstly, this HR Document Management Software research report introduces the market by providing an overview which includes definition, applications, product launches, developments, challenges, and regions. The market is forecasted to reveal strong development by driven consumption in various markets. An analysis of the current market designs and other basic characteristics is provided in the HR Document Management Software report.
Regional Coverage:
The region-wise coverage of the market is mentioned in the report, mainly focusing on the regions:
Segmentation Analysis of the market
The market is segmented on the basis of the type, product, end users, raw materials, etc. the segmentation helps to deliver a precise explanation of the market
Market Segmentation: By Type
Cloud-Based
On-Premise
Market Segmentation: By Application
Large Enterprises
Small and Medium-sized Enterprises (SMEs)
For Any Query or Customization: https://a2zmarketresearch.com/ask-for-customization/654644
An assessment of the market attractiveness with regard to the competition that new players and products are likely to present to older ones has been provided in the publication. The research report also mentions the innovations, new developments, marketing strategies, branding techniques, and products of the key participants present in the global HR Document Management Software market. To present a clear vision of the market the competitive landscape has been thoroughly analyzed utilizing the value chain analysis. The opportunities and threats present in the future for the key market players have also been emphasized in the publication.
This report aims to provide:
Table of Contents
Global HR Document Management Software Market Research Report 2022 – 2029
Chapter 1 HR Document Management Software Market Overview
Chapter 2 Global Economic Impact on Industry
Chapter 3 Global Market Competition by Manufacturers
Chapter 4 Global Production, Revenue (Value) by Region
Chapter 5 Global Supply (Production), Consumption, Export, Import by Regions
Chapter 6 Global Production, Revenue (Value), Price Trend by Type
Chapter 7 Global Market Analysis by Application
Chapter 8 Manufacturing Cost Analysis
Chapter 9 Industrial Chain, Sourcing Strategy and Downstream Buyers
Chapter 10 Marketing Strategy Analysis, Distributors/Traders
Chapter 11 Market Effect Factors Analysis
Chapter 12 Global HR Document Management Software Market Forecast
Buy Exclusive Report @: https://www.a2zmarketresearch.com/checkout
Contact Us:
Roger Smith
1887 WHITNEY MESA DR HENDERSON, NV 89014
[email protected]
+1 775 237 4157

Related Reports:
Microgreens Market to Witness Robust Expansion by 2029 | AeroFarms, Fresh Origins, Gotham Greens
Online Booking Systems Market to Witness Huge Growth by 2029 | Shedul.com, Bitrix24, Amidship
Remittance Market to Witness Growth Acceleration | Western Union, bridge21, RIA Money Transfer
Load Bank Rental Market Report Covers Future Trends with Research 2022-2029 | SUNBELT RENTALS, ComRent, Kaixiang
VoIP Softphones Market Scope and overview, To Develop with Increased Global Emphasis on Industrialization 2029 | Nextiva, RingCentral, Jive Communications
Transformers and Services Market with Tremendous growth by 2029 Emerald Transformer, Vertiv Group Corp, ABB
Energy Storage System for ShipsMarket Analysis, Research Study WithRolls-Royce, Leclanche, SAFT
Wall Stickers and Wall Decals Market Is Expected to Boom-Vinyl Impression, INQEO, Wallboss
Ice Cream and Chocolate Market Set to Witness Explosive Growth by 2029 | Nestle, Oregon Ice Cream, Unilever
Microgreens Market to Witness Robust Expansion by 2029 | AeroFarms, Fresh Origins, Gotham Greens0

COMTEX_410673913/2769/2022-07-21T09:22:56

The future holds many opportunities to incorporate technology into a business, hence it is essential to set time within a company to research current…
Inadequate privacy safeguards and the stockpiling of sensitive customer information have made Australia a target in the eyes of foreign hackers.
British Airways will permit all cabin crew to wear make-up and accessories regardless of gender.
Crisis-struck cryptocurrency platform FTX has gone bankrupt in the United States and its chief executive Sam Bankman-Fried has resigned.
COPYRIGHT © 1998 – 2022 DIGITAL JOURNAL INC. Sitemaps: XML / News . Digital Journal is not responsible for the content of external sites. Read more about our external linking.

source

Last November, the document management company NetDocuments acquired Afterpattern, a no-code toolkit that law firms and legal teams can use to build apps and automate legal documents and workflows, promising at the time that it would be natively integrated into the NetDocuments platform.
Today, that promise comes to fruition, as NetDocuments releases PatternBuilder, a document and workflow automation tool that enables law firms, legal teams, and the public sector to automate their expertise and processes so they can be repeated predictably.
While PatternBuilder’s functionality is much the same as the Afterpattern product, the significant difference is that it is native to the NetDocuments platform, meaning that it is directly available for NetDocuments’ customers to use directly within the platform in which they are already working.
PatternBuilder’s App Builder provides several built Page Blocks to choose from, making it easier to build apps while also enabling users to create the complex interactions needed in legal document automation such as looping and iterations.
“Built directly into the NetDocuments platform, organizations of all sizes will be able to leverage this new capability while inheriting all of the security, governance and accessibility benefits of being in the cloud,” said Josh Baxter, NetDocuments CEO.
The core use case for PatternBuilder is to enable legal professionals to replicate and automate their unique templates and processes so that they are done consistently every time.
With the product built natively into NetDocuments, it enables firms to embed document assembly directly within the document management system, populating user inputs into Word and PDF documents and then automatically saving those documents into the folder or workspace the user chooses.
PatternBuilder Global Apps Page enables apps to be run from within the NetDocuments browser interface. All menu options shown are rights dependent and fully configurable at a granular level.
NetDocuments says that PatternBuilder has several unique features that make it easy for its customers to get started with automation:
“Being able to automate both simple and complex documents and tasks, as well as manage and implement these new applications, is critical for legal professionals and their support teams,” said Dan Hauck, NetDocuments chief product officer. “PatternBuilder gives organizations the ability to scale their expertise and consistently deliver their best work.”
PatternBuilder is officially launching today in the United States and will be rolled out to other regions during September, the company said.
It is being sold as an add-on product with the NetDocuments’ DELIVER solution, which consists of tools and features designed to enable legal organizations to safely organize, package and share content with clients, customers, outside counsel, and other internal and external groups.
NetDocuments says it plans to continue to enhance and add features to PatternBuilder. Over the next few months, it said, it will release the ability for users to:
Current Afterpattern customers will be able to continue using the product. However, Afterpattern will no longer accept new customers.
 
Bob is a lawyer, veteran legal journalist, and award-winning blogger and podcaster. In 2011, he was named to the inaugural Fastcase 50, honoring “the law’s smartest, most courageous innovators, techies, visionaries and leaders.” Earlier in his career, he was editor-in-chief of several legal publications, including The National Law Journal, and editorial director of ALM’s Litigation Services Division.

Bob Ambrogi is a lawyer and journalist who has been writing and speaking about legal technology and innovation for more than two decades. He writes the award-winning blog LawSites, is a columnist for Above the Law, hosts the podcast about legal innovation, LawNext, and hosts the weekly legal tech journalists’ roundtable, Legaltech Week.

Receive a weekly digest of all new content.
You have successfully joined our subscriber list.

ABOUT LAW SITES
LawSites is a blog covering legal technology and innovation. It is written by Robert Ambrogi, a lawyer and journalist who has been writing and speaking about legal technology, legal practice and legal ethics for more than two decades.

source

Review your content’s performance and reach.
Become your target audience’s go-to resource for today’s hottest topics.
Understand your clients’ strategies and the most pressing issues they are facing.
Keep a step ahead of your key competitors and benchmark against them.
add to folder:
Questions? Please contact [email protected]
The guide below provides some useful information on acceptable descriptions of metaverse-related goods and services in Canada, the United States (U.S.), The United Arab Emirates (U.A.E.), the European Union (EU), and Singapore.
Given the emergence of virtual worlds and the metaverse, brand owners may wish to assess their own trademark portfolios with a view to expanding coverage to encompass this developing space. Virtual worlds permit the movement of digital goods themselves, and trademarks designed for real life goods may not necessarily extend to those digital worlds, depending on their application. In addition to considering potential enforcement mechanisms in the metaverse, brands can consider a proactive approach, with a view to creating protection strategies and potential language for filing trademark applications with respect to virtual worlds and digital elements.
As more creative metaverse-related uses emerge, goods and services will continue to be defined, more guidance will be issued, and the list of acceptable terms should further proliferate. In the meantime, we invite you to contact us for guidance in drafting potential new descriptions including, in some instances, strategizing with respect to populating the listing in the Canadian Manual of Goods and Services with proposed descriptions.
Descriptions of goods and services for the virtual/digital world field in:
Canada
We invite you to consider the goods and services currently recognized by the Canadian Trademarks Office and have listed a few examples in this article. While descriptions of goods and services that are not included in the Canadian Trademarks Office’s Manual of Goods and Services may still be acceptable if described in ordinary commercial terms (terms commonly used in the relevant industry to describe the goods and services), filing applications in Canada using goods and services descriptions that are listed in said Manual will allow applications to reach the examination stage faster and will avoid Examiner’s reports based on goods and services descriptions.
Virtual goods and cryptoassets including NFTs
Brands have begun experimenting with Non-fungible-tokens (NFTs) which have recently dominated headlines. The Canadian Trademarks Office recognizes a number of descriptions of goods (G) and services (S) with respect to NFTs and other cryptoassets encompassing generally classes 9 goods and 42 services.
Acceptable descriptions for NFTs and other cryptoassets in Canada include the NFTs themselves or software for an action related to the NFTs. Examples are goods that generally fall in Class 9 as follows:
Services related to cryptoassets including NFTs
In an alternative, acceptable descriptions can include services for cryptoassets including NFTs, such as platforms that provide an action with respect to NFTs. Examples are services that generally fall in Class 42 as follows:
Electronic transfer of cryptoassets
The electronic transfer of these cryptoassets can fall within Class 36:
Software for use in the metaverse
Examples of metaverse applications may take the form of software, games, digital goods (including “skins”), or avatars or the like for use in the metaverse that generally fall within Class 9.
Metaverse-enabling hardware
These metaverse applications may also take the form of hardware, such as head-sets, which enable virtual reality platforms. Pre-approved terms generally fall in Class 9:
Unsurprisingly, the sale of these goods may fall into Class 35:
Marketplace for virtual goods
When the service being described is a marketplace for virtual or digital goods, the description will typically fall into Class 35.
Services for provision of virtual content
In some instances, Class 41 may also be appropriate for services with respect to the provision of virtual content. For example, the Canadian Trademarks Office has pre-approved the following language, generally in Class 41:
United States
Goods and services in the United States Trademarks Office
The United States Trademarks Office similarly has approved language with respect to NFTs, virtual goods and related services. Examples include:
Goods
Virtual Goods and Cryptoassets including NFTs
Downloadable audio and video recordings featuring {specify subject matter, e.g., sports highlights, movie clips, memes, etc.} authenticated by non-fungible tokens (NFTs) Downloadable audio recordings featuring {specify subject matter, e.g., music, poetry, etc.} authenticated by non-fungible tokens (NFTs) Downloadable computer game software featuring virtual goods, namely, {indicate goods, e.g., furniture, jewelry, sunglasses, etc.} for use in online virtual worlds Downloadable computer software for accessing, reading, and tracking information in the field of {indicate subject matter of information, e.g., patient medical records, financial transactions, etc.} on a blockchain Downloadable computer software for use as a digital wallet Downloadable image files containing {indicate subject matter or field, e.g., trading cards, artwork, memes, sneakers, etc.} authenticated by non-fungible tokens (NFTs) Downloadable multimedia file containing artwork relating to {indicate field or subject matter of file} authenticated by non-fungible tokens (NFTs) Downloadable multimedia file containing artwork, text, audio, and video relating to {indicate field or subject matter of file} authenticated by non-fungible tokens (NFTs) Downloadable multimedia file containing audio relating to {indicate field or subject matter of file} authenticated by non-fungible tokens (NFTs) Downloadable multimedia file containing text relating to {indicate field or subject matter of file} authenticated by non-fungible tokens (NFTs) Downloadable multimedia file containing video relating to {indicate field or subject matter of file} authenticated by non-fungible tokens (NFTs) Downloadable music files authenticated by non-fungible tokens (NFTs) Downloadable software for generating cryptographic keys for receiving and spending crypto assets Downloadable video recordings featuring {specify subject matter, e.g., sports highlights, movie clips, memes, etc.} authenticated by non-fungible tokens (NFTs) Downloadable virtual goods, namely, computer programs featuring {specify nature, type, e.g., articles of clothing} for use in online virtual worlds
Of course, other classes should not be overlooked when the good may primarily fulfill one purpose with the incorporation of a digital sensor that could have use in the metaverse, for example, for goods related to scanned objects to be incorporated into the metaverse with metadata and use of Internet of Things (IoT) sensors. For example, the United States Trademarks Office provides for various goods incorporating digital sensors:
Compression sleeves incorporating digital sensors (G, Class 10) Socks incorporating digital sensors (G, Class 25) T-shirts incorporating digital sensors (G, Class 25) Yoga pants incorporating digital sensors (G, Class 25)
Services
Metaverse-related retail store services in Class 35
Online retail store services rendered in a virtual environment featuring physical goods, namely, {specify type, e.g., furniture, jewelry, sunglasses, etc.} Online retail store services featuring virtual goods, namely, {specify type, e.g., furniture, jewelry, sunglasses, etc.} for use in online virtual worlds Online retail store services featuring digital goods, namely, {specify type, e.g., furniture, jewelry, sunglasses, etc.} for use in online virtual worlds Online retail store services rendered in a virtual environment featuring virtual goods, namely, {specify type, e.g., furniture, jewelry, sunglasses, etc.}  Online retail store services rendered in a virtual environment featuring physical goods and virtual goods, namely, {specify type, e.g., furniture, jewelry, sunglasses, etc.}
Some of the virtual services descriptions listed in the Acceptable Identification of Goods and Services Manual (ID Manual) of the United States Trademarks Office are not currently included in the Canadian Manual of Goods and Services. Some examples are:
Authentication of data in the field of {indicate field, e.g., works of art, financial transactions, medical records, etc.} using blockchain technology (S, Class 42) Computer services, namely, creating an on-line virtual environment for {indicate purpose, e.g., off-track betting, trading stocks, etc.} (S, Class 42) Electronic storage of crypto tokens for others (S, Class 42) Entertainment services, namely, providing virtual environments in which users can interact for recreational, leisure or entertainment purposes (S, Class 41) Financial exchange of crypto assets (S, Class 36) Organizing, arranging, and conducting virtual {specify type of sport, e.g., triathlon, cycling, running, etc.} events (S, Class 41) Providing an on-line forum for trading virtual real estate (S, Class 38) Providing on-line non-downloadable software for generating cryptographic keys for receiving and spending crypto assets (S, Class 42) Providing temporary use of on-line non-downloadable computer software for use as a digital wallet (S, Class 42) Providing temporary use of on-line non-downloadable software for accessing, reading, and tracking information in the field of {indicate subject matter of information, e.g., patient medical records, financial transactions, etc.} on a blockchain (S, Class 42) Provision of an online marketplace for buyers and sellers of downloadable digital {indicate type of downloadable digital goods, e.g., art images, music, video clips, etc.} authenticated by non-fungible tokens (NFTs) (S, Class 35) Provision of an online marketplace for buyers and sellers of downloadable digital art images authenticated by non-fungible tokens (NFTs) (S, Class 35) User authentication services using blockchain technology for {specify the application of the services, e.g., cryptocurrency transactions, online software applications, etc.} (S, Class 42)
UAE
Building on the 2017 launch of its Strategy for the Fourth Industrial Revolution (4IR), the UAE recently introduced a National Digital Economy Strategy. This announcement is in line with its generally supportive approach to crypto-related activities of the region. With a desire to establish itself as a leader in the metaverse economy in the region and among the top 10 cities globally, Dubai has created the Virtual Assets Regulatory Authority (VARA), which provides a legal framework for digital assets such as NFTs.
The region has also taken concrete steps in the digital economy with the UAE Ministry of Economy announcing the installation of official departments in the metaverse, allowing users to access services entirely virtually. Once launched, metaverse users will be able to visit the virtual office rather than the existing physical offices to provide signatures on legally binding documents. In October 2022, the Government of Dubai's Legal Affairs Department announced that from early 2023, it will move its "Continuing Legal Professional Development" training for Dubai-based legal consultants into the metaverse. The intention is to run interactive CLPD sessions in the metaverse, using AI to identify areas of further development.
These actions are in addition to other digital friendly initiatives including: the introduction of the world’s first virtual megacity in 2021 – Metaverse Dubai – based on the city’s real topography and geography; hosting of the world’s first economic summit in the metaverse – Investopia; launch of the Middle East’s first metaverse incubator – MetaIncubator among others. The UAE Trademarks Office has not, to date, issued any formal practice direction or notice in relation to goods and services relating to the metaverse, crypto assets or the like. However, the UAE officials have accepted applications in these areas.
Goods and services in the UAE Trademarks Office
We have seen trademark metaverse-related applications accepted for the following terms segmented by the following Classes:
Class 9:
Class 35:
Class 36:
Class 41:
Class 42:
EU
Guidance provided by the European Office
The EUIPO stated in a guidance document published on its website, that virtual goods should be registered in Class 9 because they are treated as digital content or images. The Office, however, specified that the mere term “virtual goods” on its own lacks clarity and precision and must therefore “be further specified by stating the content to which the virtual goods relate (e.g. downloadable virtual goods, namely, virtual clothing)”.
Similarly, the term non fungible tokens on its own is not acceptable. The specific type of digital item authenticated by the NFT must be included. This is because NTFs are treated as unique digital certificates registered in a blockchain, which authenticate digital items but are distinct from those digital items. 
Furthermore, “services relating to virtual goods and NFTs will be classified in line with the established principles of classification for services”.
Singapore
The Intellectual Property Office of Singapore ("IPOS") has similarly approved language with respect to NFTs, virtual goods and related services, although no formal practice directions for the same have been issued. Key classes for metaverse-related marks include Classes 9, 35 and 41, amongst others.
We provide several examples below that have been accepted by IPOS or can be found in the IPOS database of accepted specifications segmented by Class.
Class 9
Class 35
Class 36
Class 41
Class 42
add to folder:
If you would like to learn how Lexology can drive your content marketing strategy forward, please email [email protected].
© Copyright 2006 – 2022 Law Business Research

source

Most Popular
The National Security Agency (NSA) is urging developers to shift to memory safe languages – such as C#, Go, Java, Ruby, Rust, and Swift – to protect their code from remote code execution or other hacker attacks.
Of the languages mentioned above, Java is the most widely used across enterprise and Android app development, while Swift is a top 10 language, thanks in part to iOS app development. And there’s growing interest in Rust as a replacement for C and C++ in systems programming.  
“NSA advises organizations to consider making a strategic shift from programming languages that provide little or no inherent memory protection, such as C/C++, to a memory safe language when possible. Some examples of memory safe languages are C#, Go, Java, Ruby, and Swift,” the NSA said.
The spy agency cites recent research from Google and Microsoft that 70% of their security issues, respectively in Chrome and Windows, were memory-related and many of them were the result of using C and C++, which are more prone to memory-based vulnerabilities.
Also: Cybersecurity, cloud and coding: Why these three skills will lead demand in 2023
“Malicious cyber actors can exploit these vulnerabilities for remote code execution or other adverse effects, which can often compromise a device and be the first step in large-scale network intrusions,” the NSA notes in the “Software Memory Safety” Cybersecurity Information Sheet.
“Commonly used languages, such as C and C++, provide a lot of freedom and flexibility in memory management while relying heavily on the programmer to perform the needed checks on memory references.”
So, the agency recommends using a memory safe language where possible, whether its for application development or systems programming. 
“NSA recommends using a memory safe language when possible,” it notes.
While most infosec professionals are familiar with this debate over memory safe languages, perhaps not all developers are. Though, perhaps they should be, given it’s a decades-old problem, as Java creator James Gosling recently pointed out in a discussion about how and why Java was created. 
If anything, the NSA document offers developers a clear, plain-language explanation of the technical reasons behind moving towards memory safe languages. Probably the most discussed language in terms of memory safety has been Rust, which is the main candidate as a ‘replacement’ for C and C++. 
The Linux kernel recently introduced Rust as the second language to C, following the Android Open Source Project. These projects won’t replace old C/C++ code, but will prefer Rust for new code. Also, Microsoft Azure CTO Mark Russinovich recently called on all developers to use Rust over C and C++ for all new projects. 
“By exploiting these types of memory issues, malicious actors – who are not bound by normal expectations of software use – may find that they can enter unusual inputs into the program, causing memory to be accessed, written, allocated, or deallocated in unexpected ways,” the NSA explains. 
But – as experts have noted in debates over Rust and C/C++ – the NSA warns that simply using a memory safe language doesn’t by default preclude introducing memory bugs to software. Additionally, languages often allow libraries that aren’t written in memory safe languages.
“Even with a memory safe language, memory management is not entirely memory safe. Most memory safe languages recognize that software sometimes needs to perform an unsafe memory management function to accomplish certain tasks. As a result, classes or functions are available that are recognized as non-memory safe and allow the programmer to perform a potentially unsafe memory management task,” the NSA said. 
“Some languages require anything memory unsafe to be explicitly annotated as such to make the programmer and any reviewers of the program aware that it is unsafe. Memory safe languages can also use libraries written in non-memory safe languages and thus can contain unsafe memory functionality. Although these ways of including memory unsafe mechanisms subvert the inherent memory safety, they help to localize where memory problems could exist, allowing for extra scrutiny on those sections of code.”
Also: Cybersecurity: These are the new things to worry about in 2023
The NSA notes that some memory safe languages can come at a performance cost, which requires developers to learn a new language. It also points out there are measures developers can take to harden non-memory safe languages. Google’s Chrome team, for example, is exploring multiple methods to harden C++, but these approaches also come with performance overheads. C++ will remain in Chrome’s codebase for the foreseeable future.     
The NSA recommends static and dynamic application security testing to spot memory issues. It also recommends exploring memory hardening methods, such as Control Flow Guard (CFG), which will place restrictions on where code can be executed. Similarly, Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) are recommended.

source

(Reuters) -Thomson Reuters Corp said on Friday it would buy SurePrep LLC, a U.S.-based provider of tax automation software and services, for $500 million in cash.
The information company has been partnering since April with 20-year-old SurePrep, whose products and solutions are used by more than 23,000 tax professionals.
SurePrep is projected to generate about $60 million in revenue in 2022 and is expected to grow more than 20% annually in the next few years.
"This transaction builds on our existing partnership/reseller arrangement to deliver our vision of end-to-end tax automation that solves our customers' biggest pain points," said Dave Wyle, Chief Executive of SurePrep.
Thomson Reuters, which is the parent of Reuters News, expects the deal to close in the first quarter of 2023.
(Reporting by Aditya Soni in Bengaluru; Editing by Arun Koyyur)
Shopify is a TSX tech stock that is trading at a depressed multiple compared to historical valuations. Is SHOP stock a buy right now? The post Down 80%, Is Shopify Stock Finally Bottoming Out? appeared first on The Motley Fool Canada.
As one of the fastest-growing renewable energy sources in mitigation of climate change, solar PV is playing a major role in the future global electricity generation mix.
The S&P 500 and Nasdaq jumped on Thursday, racking up their biggest daily percentage gains in over 2-1/2 years as a sign of slowing inflation in October sparked speculation the Federal Reserve might become less aggressive with interest rate hikes. Stocks in sectors across the board surged as the latest consumer price data cheered investors worried that ongoing interest rate hikes could hobble the U.S. economy. One-time Wall Street darlings tarnished in 2022's bear market were among Thursday's strongest performers, with Nvidia jumping about 14%, Meta Platforms climbing 10% and Alphabet rising 7.6%.
The cities of the 21st century have adapted to cars just as much as they have to humans. But a new international survey by Ipsos for the mobility brand Lynk & Co shows that the common wish amongst Europeans is to use vehicles more efficiently and free up urban space for more greenery. With the average car in use only 4% of the time, Lynk & Co is challenging the industry to take a new approach to disruptive mobility.
There are plenty of great discounted stocks to buy right now, like Bank of Nova Scotia (TSX:BNS). Here's why you should invest in Scotiabank The post Should You Invest in Scotiabank Right Now? appeared first on The Motley Fool Canada.
"The concern is that more Canadians are reaching their breaking point financially," said one expert.
DETROIT (AP) — General Motors is recalling nearly 340,000 big SUVs in the U.S. because their daytime running lights may not shut off when the regular headlights are on. The National Highway Traffic Safety Administration says in documents poste on its website Thursday that having both lights on at the same time could cause glare for oncoming drivers, increasing the risk of a crash. The recall covers certain 2021 Chevrolet Tahoes and Suburbans, as well as some GMC Yukons and Cadillac Escalades. GM
Juul Labs Inc has secured an investment from some of its early investors that will keep the e-cigarette maker in business, the company said on Thursday, adding that it will also undertake job cuts as part of a reorganization. The once red-hot vaping company plans to lay off about 400 people and reduce its operating budget by 30% to 40%. The company said the investment would help Juul run its business operations, while it goes ahead with its administrative appeal of the U.S. Food and Drug Administration's marketing denial order related to its e-cigarettes.
The Canadian dollar strengthened to a seven-week high against its U.S. counterpart on Thursday as U.S. inflation pressures cooled and Bank of Canada Governor Tiff Macklem said the economy could avoid a major rise in the unemployment rate. "The U.S. dollar fell sharply in a broad-based way and the loonie has benefited from that," said Rahim Madhavji, president at KnightsbridgeFX.com. The greenback fell sharply against a basket of major currencies, bond yields tumbled and Wall Street rallied after U.S. consumer prices rose less than expected last month, data that may allow the Federal Reserve to ease up on aggressively hiking interest rates.
FRANKFURT (Reuters) -The European Central Bank is examining the use of derivatives by energy companies to make huge bets on future power and fuel prices, to see if such activity poses a wider risk to financial stability, three people familiar with the matter said. Two of the people said the inquiry was prompted by Germany's rescue of top gas importer Uniper, which like other energy firms hedged its exposures with derivatives worth tens of billions of euros, far outstripping the value of the energy it sold. The ECB's move is the first major effort in Europe to identify whether the use of derivatives by power companies poses a wider financial threat, and exposes the largely unregulated trading, which totals trillions of euros, to rare scrutiny.
The movie theatre company on Thursday reported a profit of $30.9 million in Q3, up from a loss of $33.6 million last year.
Kansas City Federal Reserve President Esther George on Thursday reiterated her support for a slower pace of U.S. interest rate increases, calling for a "more measured" approach that allows the central bank time to judge how the rises in borrowing costs are affecting the economy. "I continue to see several advantages for a steady and deliberate approach to raising the policy rate," George said in remarks prepared for delivery to an energy conference co-hosted by her regional bank and the Dallas Fed. The Fed has lifted short-term borrowing costs at an extraordinarily fast pace this year, including four straight 75-basis-point hikes that have brought the central bank's benchmark overnight interest rate from near zero in March to the current 3.75%-4.00% range.
LJUBLJANA (Reuters) -Three of the European Central Bank's most outspoken policy hawks called on Thursday for raising interest rates to a level that weakens growth in order to curb high inflation, which they said was at a growing risk of taking hold in the euro zone. With euro zone inflation running in double digits, the ECB has been raising rates at a record pace even as the euro zone economy heads for recession. This has prompted some policymakers to weigh the benefits of future increases against the risk to growth.
Qatar Airways is suing Airbus over damage to the painted surface and underlying anti-lightning system of A350 jets, which has prompted Qatar's Civil Aviation Authority (QCAA) to ground 29 of the planes over its concerns of a potential safety risk. Backed by European regulators, the world's largest planemaker acknowledges quality flaws in part of the worldwide A350 fleet but maintains its premier long-haul jet is safe. Qatar Airways said Airbus had sought to exert influence over the European Union Aviation Safety Agency (EASA) by providing the agency with a "Line to Take" document.
Roger Ng, the former Goldman Sachs banker convicted for helping loot Malaysia's 1MDB sovereign wealth fund, on Friday sued the government's star witness Tim Leissner for more than $130 million, alleging fraud. In a complaint filed in a New York state court in Manhattan, Ng accused his former boss of repeatedly lying in order to steal his investments in energy drink maker Celsius Holdings and artificial intelligence company Sentient Technologies. The complaint said Leissner, a former Goldman partner, stole Ng's money to cover his own defense costs in a related criminal case where he pleaded guilty in 2018, while depriving Ng of funds to defend himself and appeal his conviction.
Competition commissioner is challenging the deal
OTTAWA — Air Canada violated federal law by not keeping its maintenance centres in Montreal, Winnipeg and Mississauga operational during the collapse of Aveos a decade ago, the Quebec Superior Court ruled Thursday in favour of thousands of former workers. "Air Canada did not take reasonably serious steps to comply with the law after the closure of Aveos," wrote Judge Marie-Christine Hivon, who concluded that there was a "continuous violation" of the law from March 2012 to June 2016. Nearly 2,200
Loss for the three months ending Sept. 30 was US$195.2 million, compared with a loss of US$27.9 million in the same quarter last year.
Systemic vulnerabilities in investment funds and other "non-banks" that make up almost half the world's financial system will be addressed by tweaking existing rules before assessing whether more radical action was needed, a G20 watchdog said on Thursday. Central banks had to inject liquidity when money market funds ran into difficulties as economies went into lockdown in March 2020. There was also central bank intervention in Britain in September when liability-driven investment funds struggled to meet collateral calls, prompting the Bank of England to consider unilateral action in non-banks until global efforts catch up.
FRANKFURT (Reuters) -Germany's Merck KGaA reported better-than-expected quarterly earnings on higher revenues from drugs and biotech lab equipment, but signalled that growth of its semiconductor chemicals unit could lose momentum next year. The diversified group narrowed on Thursday its full-year target range for adjusted EBITDA to between 6.80 billion and 7.20 billion euros, against a previous forecast of 6.75 billion to 7.25 billion. Merck said the outlook for its life science unit, which makes substances and gear for drugmakers, had brightened further after cost cuts and as drugmakers upgrade their lab equipment to pursue new technologies.

source

Live Webinar and Q&A: How To Build Payment Systems That Scale to Infinity (Live Webinar December 13, 2022) Save Your Seat
Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Back to login

Back to login
In this article, we introduce the topic of code obfuscation, with emphasis on string obfuscation. Obfuscation is an important practice to protect source code by making it unintelligible. Obfuscation is often mistaken with encryption, but they are different concepts. In the article we will present a number of techniques and approaches used to obfuscate data in a program.
Susanne Kaiser is a software consultant working with teams on microservice adoption. Recently, she’s brought together Domain-Driven Design, Wardley Mapping, and Team Topologies into a conversation about helping teams adopt a fast flow of change. Today on the podcast, Wes Reisz speaks with Kaiser about why she feels these three approaches to dealing with software complexity are so complementary.
Roksolana Diachuk discusses how to use modern data pipelines for reporting and analytics as well as the case of historical data reprocessing in AdTech.
Audun Fauchald Strand, Truls Jørgensen describe how they have succeeded to align their teams by using: Internal tech radar increases communication between teams, and a weekly dive on a specific topic.
The need for high-quality DevOps personnel is skyrocketing, but it is harder than ever to find enough staff. It is possible to augment your DevOps organization using no-code and low-code tooling. Low-code and no-code tools can free up existing developers by reducing the time spent on integrating and administering DevOps toolsets.
Make the right decisions by uncovering how senior software developers at early adopter companies are adopting emerging trends. Register Now.
Adopt the right emerging trends to solve your complex engineering challenges. Register Now.
Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.
InfoQ Homepage Presentations The Journey to API Management on the Cloud
The panelists explore how to build, integrate, and expose services as managed APIs in the cloud to follow best practices and manage large deployments.
Asanka Abeysinghe is Chief Technology Evangelist @WSO2. Matt Morgan is Senior Director, Software Engineering @PowerSchool. Viktor Gamov is Principal Developer Advocate @Kong. Kevin Swiber is API Lifecycle & Platform Specialist @Postman. Renato Losio is Principal Cloud Architect @funambol.
InfoQ Live is a virtual event designed for you, the modern software practitioner. Take part in facilitated sessions with world-class practitioners. Hear from software leaders at our optional InfoQ Roundtables.
Presented by: Tobi Knaup – co-founder and CEO, Dan Ciruli – VP of Product
Presented by: Alex Lunev – Director of Engineering, Keith McClellan – Director of Partner Solutions Engineering
Losio: Before going into the discussion, just a couple of words, what we mean by API management and API management on the cloud. We want to discuss basically, what are our best practices? How do we manage large deployments? What is the role of integrating software and API to connect application and data that is growing every day? How can we effectively do that on the cloud? How can we do API management on the cloud? How can we integrate existing services? How can I manage them as APIs?
My name is Renato Losio. I’m an editor here at InfoQ. I’m a cloud architect. We are joined by four industry experts on API management. I’d like to give each one of them an opportunity to introduce themselves and also to share about their own journey to API management, specifically on the cloud.
Gamov: I’m a developer advocate at Kong. I do all the things around cloud connectivity right here with Kong. That includes APIs that we expose to the outside world, but also APIs that we expose within the organization and how to provide tools, so developers can build APIs as well.
Swiber: I’m Kevin Swiber. I’m an API lifecycle and platform specialist at Postman. Postman is a developer productivity tool for producing and consuming APIs. My day-to-day consists of a lot of things, but among them is talking to folks about where they are in their API lifecycle and platform strategy, and how to improve that on a day-to-day basis. I’ve been in the API management space working in API vendors for the past 10 years. I am the Marketing Chair for the OpenAPI Initiative.
Morgan: I’m Matt Morgan. I’m Senior Director of Software Engineering with PowerSchool. I came into PowerSchool last year along with my product NaVi, as we were acquired from another company. I spend a lot of time working on integrations with other PowerSchool products. We’re a multi-tenant SaaS product. We’re integrating with other multi-tenant SaaS products. We’re integrating with single tenant on-premise products. Lots of API work. I like working with APIs because it allows developers to communicate without having to understand the underlying technologies. We run in AWS cloud, and we’ve heavily been leveraging serverless. Some of the other products we’re integrating with use a variety of different technologies and clouds, and basically, anything you can imagine.
Abeysinghe: I’m the Chief Evangelist at WSO2. I tell WSO2 story. In addition to that, providing strategic consulting for various customers, including API strategy. When it comes to WSO2, we provide API management products in open source, SaaS, as well as in private cloud. That’s how we are contributing. My experience goes a long way. Actually, in 2011, I wrote a blog about API management and then that’s how WSO2 started getting into API management. I have a close relationship with this subject.
Losio: I will actually start with you with the very first key question, because I’m definitely not an expert. What are the key differentiations between API management on the cloud and on-premises, whatever cloud provider, Matt mentioned AWS, but it can be Azure, it can be whatever else you like.
Abeysinghe: That’s where we need to be a little bit careful because I think lift and shift is a common pattern we see in the industry, people take the on-prem stuff, and just put as it is on the cloud. We see the same pattern happening in API management as well. That’s the first differentiator that we need to lift and shift gears as the first step, but then we have to optimize the workloads that we are running on the cloud, to utilize the cloud capabilities as well as to optimize the resource usage, because resource usage directly correlates with the cost factor. That’s the first difference that I see.
Then the second thing is the latency requirements. Because not everything is running on the cloud, there are certain components that might be running outside the cloud environment. We need to look at how we can optimize some of these interactions that we are doing with various data sources and systems and subsystems. We need to plan it properly, and utilize as much as the cloud capabilities provided by the underneath infrastructure provider is another thing that we need to consider when it comes to API management on the cloud.
Swiber: Of course, everything Asanka said was great. A little history here is that we used to see either/or. We used to see folks with an API management solution that was cloud hosted, or one that they had on-prem. These usually were fairly large deployments that took often outside traffic coming into their internal systems. Over time, and with the explosion of microservices, we really saw this movement into a multi-gateway world. Folks typically aren’t choosing between on-prem or cloud for every scenario now. It’s usually a case of we’ve got some cloud hosted stuff for our external traffic coming in. With the explosion of microservices internally, we have an internal on-prem solution for managing those as well.
Losio: Actually, here I already immediately jumped to a question that I know is going to be a bit controversial, but I throw the topic, is like, if you develop just in the cloud, if you’re coming from a cloud background, and you are leveraging your microservice inside a single provider, whatever that provider is, when is the point when you really feel like, do I need to have an external API management solution, a third party one? Why do I actually need it? When is the point where I need to do that step?
Morgan: When do we get into a third party to help manage our APIs?
Losio: Yes. I see the extra features or whatever. It often is, when I see something external, the first thing that comes to my mind is complexity, extra cost. It’s always balancing. I never really know when is the point where it’s too early or too late?
Morgan: Too early or too late to bring in a tool to help manage the APIs? I think there’s definitely a too early stage here. If you’re just in the inception phase, and you just have an idea for a product, I want to sell T-shirts on the internet or Facebook for pets or something like that. I don’t think I would start architecting that thinking about API management. I think I would start thinking about, what’s the user experience here? How can I get that to market? How can I get some feedback on that? Start trying to sell this and grow my company, or something like that. I think the API management can come in a little bit later than that. Then, are you using something that is a third party or something from a cloud vendor? I think that really comes down to, what is your cloud strategy, and what compliance you may be facing? How do you think of the competitive space? What managed services you want to leverage. I do think that there probably becomes a point where you reach a level of success where you say, ok, now I’m starting to have some technical debt. My developers can’t discover the APIs, or it’s difficult to understand what my system is offering. At that point whether it’s an open source product, or some vendor that comes to help, I think that’s the appropriate time.
Gamov: For me, it’s a very easy question, because we’re an infrastructure provider company, so we need to make sure that whoever use our tools, they will be successful regardless if it’s the cloud or on-prem, or if they want to run this in a heterogeneous space. Like Kevin mentioned this, that these days, it’s not a question about going into cloud, it’s a question more about how many clouds. Because what we see is that many customers actually run either as two hot deployments, and that want to have a unified communication between those systems, or they might be running this as one system as a backup. Even though it’s a backup, there needs to be a configuration that will replicate the status of the main production, all these things. In my world, those things are API management, API lifecycle management. Also goes together with configuration management, and together with automation. All things that we learn how to love in a DevOps world also comes together with API world. Things around the API Ops. Many things that we learn from the tools, and automation things that are available for delivering software API, it’s another software that we deliver through those tools.
Losio: Actually, you mentioned an interesting topic as well, Kevin, before about the multi-cloud, multi-policy. It’s hard now to find a large enterprise that is just one, either in-house or either one single provider or whatever. I was thinking, if I now have to choose something, if I need to change or start work in API management, I have two standard feeling, one is on the cloud. One is the cloud lock-in that I might be stuck, whatever is reasonable or not with that vendor that what I’m using from that specific cloud provider, whatever it is, AWS, might force me to stay or might make my transition to another cloud provider difficult. Or if I use a third party vendor, is there going to be something that I can change later on? I was wondering if anyone has any feedback about that, whatever we call it, vendor lock-in, or whatever you want to call it, tools risk, OpenAPI Initiative.
Swiber: I’ve been in the API space for 10 years. My opinion is probably going to be somewhat biased, but my life prior to that, I was in enterprise architecture for several businesses. This question becomes really important on vendor lock-in. I think my feelings have progressed on this throughout the years, as I’ve noticed that vendors aren’t really the only way you get lock-in. I can get lock-in to a frontend framework. How many folks have successfully migrated off of React after finding a solution that they thought might be better? Very few. You end up getting really stuck to this infrastructure that you put in place. When it comes to something like API management, yes, I think there is going to be a certain amount of vendor lock-in that happens when you make that decision. Some of the criteria around making that decision needs to be around the vendor itself. Is this someone who’s going to be a strategic partner for me as we continue to grow? Is this someone who’s going to help influence us as we can help influence the product and help them, and we can grow together? I think vendor lock-in feels very scary. The reality is that you are already locked in in several different ways. The truth is, how do you evolve with that reality going forward? It’s not an easy decision in a lot of places.
Abeysinghe: I completely agree with Kevin. There are some lock-in when it comes to the software development and running this stuff in different environments. Only one area that I would like to highlight, the gateways are becoming a commodity. That’s where the standards are becoming very important as well, as you mentioned, OpenAPI specifications, AsyncAPIs, GraphQL. Things are getting standardized. Even we are not building API Gateway anymore, it’s just Envoy, because that’s becoming a commodity. Then there are other parts associated with API management. That’s where the real vendor lock-in comes in, how you manage the lifecycle of the APIs, observability, and security. All these things are running in the control plane, so the data plane is getting more commoditized, but the state of the control plane is having some vendor specific components. Even we started something called API Federation specification some time back, but we didn’t get much support from the industry. I think we need to have more of those type of initiatives and get some of this stuff standardized. That way, we can provide a flexible environment for the end users to switch or do whatever that they would like to do. Because end of the day, if we provide a better product, they will stick. That’s how the experience economy market is running at the moment. That’s how I see this from a vendor point of view.
Gamov: It’s very difficult not to be triggered when everyone is saying, Envoy is all the things, but Nginx, and Kong is based on Nginx, was there, and still there, and still plenty of innovation happening in this space. I would not just dismiss this, again, also very biased, and that’s why I need to say this. Envoy is an incredible tool and many software tools that we built like service mesh, for example, that uses Envoy. However, it’s still a new technology and a technology that’s getting very wide adoption, however, still, roughly 80% of internet runs on Nginx. In this case, Envoy still needs to go a very long way to win hearts and minds. Speaking about Envoy, we got this very interesting roundtable on the recent ServiceMeshCon in Valencia, and everyone was actually complaining about the sidecars and having Envoy as another step of the infrastructure. It’s an interesting situation, interesting state, and depends on what vendor we’ll be talking about their tech. I’m totally completely transparent about this.
Losio: You made a good point that 80% is still running on Nginx. When we think about API management and adoption curve. Because when you go to a conference, you’re always a bit biased, because it’s like you always talk to guys that if I go to a conference, 100% of the company are running Kubernetes somehow. Even if I go out of there it’s a high number, but it’s not 100%. I was wondering as well, with API management, more so thinking about enterprise, because of course, as we said before, maybe a small company, someone started maybe, they might use it, but maybe it’s not there yet. How do you see API management, at the moment? Do you see it as an early adopter phase or already early majority, or even just few innovators? Where are we compared to a couple of years ago?
Morgan: Honestly, I haven’t seen a whole lot of change in that space. I think we’re building APIs with different tools. Ten years ago, we were pretty much all in data centers. Cloud was just getting started. Containers were starting to pop up. OpenAPI was there. Nginx was there. I think we have to build an integration. Yes, we built it, and then there’s not really any documentation or any follow-up from that. That was there. I think that’s still there, and it’s still something that we struggle with as an industry. I’m doing serverless, so I’m using Amazon API Gateway and EventBridge, and services like that to build APIs. That’s a change. The one thing that’s changing there, at least for me, is I’m thinking more about asynchronous APIs. I’m thinking more about like, what is the contract? There’s an AsyncAPI foundation out there too, to go along with OpenAPI. What is the contract of this asynchronous workflow? What do the payloads for that look like? What does it do? It tries to solve the same problem that OpenAPI does, so that we can communicate, what does that asynchronous workload look like, in a non-technology specific way?
Losio: Kevin, have you seen any change recently in that space?
Swiber: I think first of all when we talk about API management, it’s helpful to put some definition around that, because the definition of API management has really broadened over the last 10 years. It used to be APIs were an integration point. You would focus on things like protocol mediation, maybe some caching. Then folks started looking at APIs like a product, and then having things like a developer portal would be really interesting there, and making sure authentication was in the right place. We’re to a point now where instead of trying to convince folks, as an industry, like yes, we need APIs, we’re at a place where people have so many APIs it’s hard to manage. They’re talking about, do we have the right testing strategy? Do we have governance in place? Do we have discoverability of our APIs? If we go back to those initial origins of integration points, that stuff is probably moving over to late majority, perhaps laggards now. If you look at some of the newer stuff, API as a product thinking is still gaining traction and hasn’t peaked yet. The idea of developer portals, they’ve been out for a really long time, but they’re starting to really get some momentum on iterating, and changing even faster into this new world where we have an explosion of APIs that we need to manage. I don’t think it’s as simple as saying, like all of API management is on this maturity path. There are bits and pieces all over the place. I think we’ll continue to see that grow and change over the next few years.
Losio: Actually, what you mentioned really reminds me what actually Matt said as well on AWS, the API Gateway. Yes, it’s true. Many people are using it. I never saw so much excitement about a new feature for Lambda recently when they announced that you could call a Lambda through a URL, going around the API Gateway entirely. That brings its own problem, but it shows how many people actually were using API Gateway, because they had to do it. If they could avoid it, they would even avoid it. It’s not a straightforward answer.
Gamov: For your particular example, I think it’s more about the overall strategy that Amazon as a company start blowing out, because some of the products just exist, and some people do use them, some people don’t use them. That’s why smaller vendors like WSO2, Kong, and others, they have bigger ideas. They can innovate in the space because they have an overall bigger picture. For Amazon, it’s just another thing that they can sell. For us, we want to have an overall experience. I will double to what Kevin said when we were talking about the vendor lock-in. We don’t want to have vendor lock-in. We understand that our customers are smart enough to pick up a good solution for them. We want to be the best partners for them. That’s why for some companies like Google, like Amazon, the gateway is something that they will just throw for your discount, as a change for your EC2 instances or for your Lambdas. There is overall strategy around API management, API building, developer portals, collaborations around how to build those APIs, and overall approval process of using tools like GitHub, and GitOps, and things like that. This is the part where smaller vendors can innovate and can show actual value for the customer, and become a right partner for the customer, so they would see value of applying those tools. Not just, ok, so let’s go call the Lambda URL directly without rate limiting, without caching, and see how we continue swiping our credit card.
Losio: I was absolutely not recommending that. I was actually thinking that there are some scenarios where it could help, a very small link or whatever where you might not need the complexity of the gateway. I can see very bad uses of that. I was just using that as an example.
Gamov: If something is possible, it doesn’t mean you have to use it.
Abeysinghe: I think there are two sides of this story, as witnessed how the products are matured, and the capabilities are matured. I think collectively, all of us, we have contributed a lot, and then brought API management into a great state. There can be many standards coming in the future, and we will support it. From the user point of view, I think it’s a very geo sensitive thing. If you look at North America, it is more into late majority, but the rest of the world, it is early majority. That’s how I see, if you look at it from the user point of view.
Losio: You’re basically suggesting that it is not just between large companies and smaller company, but as well, really the area of the market where geographically it is more mature.
Abeysinghe: I think generally technology adoption happens like that. A lot of people watch what’s really happening in North America, and then sometimes Western Europe capture most of this stuff, and then it flows to rest of the world. That’s what we see as a pattern for a long time. I’m not telling the innovation doesn’t come, but innovation does come but that’s a common thing.
Gamov: I concur. Things like for example open banking standard, like quite mature in Asia-Pacific and Australia. We have some customers who invested a lot in open banking, and after Europe picking up, and America is not near close to the open banking initiative. In the banking space, you start seeing things like, finally banking allows you to use OAuth 2.0 to access APIs, because in the past, you need to enter login and password. Now, more banks allow to integrate the system. This innovation actually comes from the smaller companies, like Okta. The standards and the innovation comes from the small company, but I agree in terms of geography, it’s also important.
Losio: I know that none of you has a crystal ball, but where do you see the market going in 5, 10 years? Not just in terms of growing, hopefully.
Gamov: I hope it will grow, because last couple weeks the market was not in a fun place.
Losio: I was wondering, mainly, if we’re still going to talk about it, there is going to be that mature technology and part of pipeline.
Swiber: I work with tons of folks today on the challenges that they’re facing. A lot of folks are just really getting started trying to get some governance in place, consistency between APIs, some management around who’s producing APIs. Where are they going? We see terms coming out like shadow APIs, APIs that exist that you don’t even know were there. Zombie APIs, APIs that aren’t getting used anymore. I think this is only going to continue, as we try to get a handle on this over time. As Matt was saying, this definition of APIs, and what is an API is really expanding to include event driven systems. I think we’re just beginning to see AsyncAPI take off as a sister standard to OpenAPI, and this event based or message based protocol. I think we’ll see lots of innovation happen along the async path over the next few years as well.
Morgan: I agree. The thing that I see becoming more prevalent is more managed services, more things where you don’t have to rack hardware or things like that. All the clouds are doing that thing. You also have smaller vendors that are also getting into that space and are providing more managed services. Every day it seems like there’s a new web based SQL offering or something like that, where I can just make API calls to a SQL database that’s globally available. Those things I think are really amazing. If you don’t want to be in AWS or you don’t want to be in Google Cloud or something like that, but there are really great vendors out there that are doing some really interesting offerings. I think we’ll see more adoption of those. We’ll see more good options to build with. I think those kinds of services are really great for builders, because you can just get building and you don’t have to install MySQL, and configure all that. I think we’ll see more of that in the next 10 years.
Abeysinghe: I think it connects with what Jeff Lawson said about build versus buy. Buy the platform and build the innovation on top of it. Because then we can focus more on the innovation side, because if you talk to CIOs and CTOs, they are building platforms, and most of the development teams are even supporting platform engineering teams to get these things up and running in production environments. That’s the key challenge. If we get the correct platform, especially like a SaaS platform that provides the infrastructure and have the flexibility for the organization to configure it in the way that they want, then you can focus on the application development and focus on the customers. That’s how I see. I completely agree with Matt and Kevin on that.
Losio: That brings us back to the topic of how to sell it to a developer. I’m a developer. I’m working with my few services on AWS, try to build, mix and match. Probably, I’m using some API without even realizing, but suddenly, someone told me that I should focus on API management, or actually even worse, someone brought in something new that I have to work on it. How do I sell it to developers the main advantage of doing API management on the cloud? Where, as you said as well, Matt, the concept of the service is going to be managed, most likely I don’t have to run my own server. What’s the biggest benefit as a developer to introduce an API management system? If there is an advantage.
Swiber: It gets us back to that definition of what API management is. We’re taking a broad view of what API management is, and saying that it starts when you begin collaborating on an API. It includes the testing of your API, it includes designing what your API is going to look like. Then all that stuff comes in early. Folks, developers, if they’re not using any help for this, they’re already experiencing issues around collaboration and how to get that done. It could be as simple as saying actually, you probably need it right now. When we talk about the runtime components of that, we talk about things like authorization. There is a case to be made to a lot of folks that, A, again, these conversations should be happening early in your process, how are you securing your APIs? B, how do you want to manage the security of those APIs? Do you want that to be distributed across every team, or do you want some centralized management around that? Do you want some rules in place to help you do that? Do you want some guides? Do you want some infrastructure, some software to help you do that? I think folks get to the runtime side through authorization requirements, more often than not.
Losio: Does that depend usually just on the size of the company. Of course, I can see that if I have a development team of 3 people versus 300, probably I have different requirements in the sense of standardizing and centralizing. Do you see cases where I need actually to do the next step when I’m still in an early phase, or with a very small engineering team, or usually something that you do at a later stage on existing deployments?
Swiber: For me for even early stage folks, I’m seeing them move to API management solutions for this as well.
Gamov: You’re absolutely right. What I would just point out, it’s not about the size of the team. It’s more about the maturity, about engineering maturity, when the team is quite proficient on the things like 10x engineers. 10x engineers, they understand that, at some point, they need to grow, they need to collaborate, and especially if they’re in the world of microservices, this stuff will come with a price. There’s two approaches of how teams are taking this. One is a schema first. They use OpenAPI spec defined all this contract. That’s why it works for the teams where they have a dedicated team for backend and dedicated team for frontend and dedicated teams for mobile maybe. I don’t remember who mentioned this term, about the API as a product. Even it’s also internal because your API consumers are internal, you have teams who do frontend, teams who do mobile. It’s still a product. In this case, you need to have some sort of removing this roadblock so that people can start working on the frontend once the spec is there, even backend maybe it’s not ready yet.
Another approach is to use code first. The people develop APIs. Usually, this is like a legacy approach. The people already start building this, and all of a sudden, they understand they need to document this, they need to publish on the developer portal, because other people need to use it somehow. That’s why they use some generators to generate OpenAPI spec based on the running spec. This is where engineering maturity comes into play. Because if you’re following like a schema first, it requires some discipline and require a certain level of expectation, because many people will be involved, and there should be some process to establish it. In many cases, people cannot wait. They say, are we in the waterfall again? Why are we not agile anymore? That’s what I see happening.
It also somehow correlates to the sizes of the teams and the sizes of the companies. In the startup space, maybe it’s not so much important, because this stuff will be rewritten very soon, maybe after six months, or after a year. Because some of the iterations of the software in the startups, they can move faster, they can rewrite things faster, they can iterate and fail. If it’s a big organization that involves API as a product, everyone embraces microservices, and they’re ready to go and sell internally, like give the service for shipping code.
Abeysinghe: We can’t avoid the programming models and the design principles that are bound to APIs, so we had to accept it. That’s there. I think the responsibility of a developer, that’s the key thing. How much he or she is responsible about the API that they expose, because as an example, I found the situation that one API went down, and around 200 applications got affected, assume number of users who are getting affected from 200 applications. That’s the impact. I think the transactions are going through these APIs, and the business value that these APIs are carrying is really high. That is a thing that the developer should identify. That’s where the API management is coming, like how we can have proper versioning. How we can manage this API, use the standards and go through the organization standards that they have defined for the APIs, all these things matter. I think size of the organization doesn’t matter. The key thing is who’s consuming. If it is a shared API, I think that particular team should focus on API management. There’s a runtime component as well, like how healthy, and whether it’s providing the business benefits. How you can manage these APIs in that production environment, all these things matters. I think it’s a good thing to think but how complicated and what extent that this development team is stepping into, is depending on the maturity of the entire application that they are building.
Losio: Actually, Viktor raised an interesting point about saying that startups will have any way to rebuild everything. I was thinking, I start a new startup. I’m in a young and foolish and whatever, I’m working on this new cool idea, and here, I say I don’t have time to think about API or to think about doing things properly. I’m mainly thinking about go live as soon as possible. Then I think about that later, because I will need to redevelop it. Is that fair enough to say I shouldn’t care, or I should start in the cloud, I have an easy way to start already with API management? I have really no excuse not to do it.
Morgan: I don’t think you should get too hung up on the nuts and bolts when you have a great idea. I think you should drive ahead on that. If you have some expertise to use something like AWS Amplify, or Google’s Firebase, or one of these things where you can spin up an application very quickly, you don’t have to manage the database. It could be a third party. It could be FaunaDB, or MongoDB, or Vercel. There’s a whole bunch of products out there. If you have any expertise to use this, I would strongly recommend doing that. If all you know is Ruby on Rails, build your application that way, and find a server somewhere. I think there are a lot of great tools to build on. I don’t know if in the heat of the moment as you’re trying to launch your brilliant idea is the great time to learn serverless, or some of those other things. Those are good skills to have, and I would apply them if they’re available.
Swiber: I think it depends on what you’re doing. If you’re building just a single web application that you’re putting out there, maybe not. If you have been bitten by this API first bug, and you are building an API as a product, then API management should absolutely be something that you’re looking at to help launch that. Again, there’s a lot that comes with that, how are you going to reach your consumers, developer portals and things like that? Are you giving your developers the best experience? Because that’s going to determine success on top of the value that you’re providing. Is that experience good? What tools are going to help you get there? I know for me maybe it takes me a little bit longer than some folks to catch on to things, but I need to be hands-on with this stuff. I need to have some experience actually going through and playing with these tools and seeing how they work. There’s tons of free open source stuff out there, or trial tier. Would definitely recommend folks get their hands on that and play around with that if they have the time. Again, as Matt said, if you’re launching something, it’s got to be today, and you’ve got the expertise for something that wouldn’t require a whole set of infrastructure, then absolutely go that route, because your speed to market is going to be important.
Abeysinghe: I think Kevin and Viktor, we have a role here as well to simplify the tools, and then make it easy for the developers. As long as we do that thing, I think then anybody can start getting hooked to the API management cycle, and then get the benefit of it. We have done a lot, especially Postman, I think, very popular among the developers because of that simplicity, as well as how it is affecting the productivity of the developers.
Gamov: As well as Insomnia, also getting a lot of attention on collaboration aspect recently. We’re certain that the approach with a GitOps, and automation, and CI/CD things that help to simplify and maybe eliminate some errors, it’s very important. That’s why, like in Insomnia, which is also a great tool, we’re spending a lot of time to do the thing that Kevin mentioned. Like you’re a new guy joining the company, you want to discover what kinds of APIs are there, like are there zombie APIs that no one is using? Or, what are those APIs that are available? Having the ability to immediately pull up the repository of the things that are immediately available for you as a developer, and you can start building things. That’s incredible. Collaboration and automation, that’s the keys for success, regardless if you’re a startup or if you’re a smaller or you’re a bigger company.
Losio: I wanted to ask each one of you for a very quick advice. It’s like, I want to do something. I want to start to act in that direction, to think a bit more about API management that I never thought before. What should that be?
Morgan: I think the main thing to focus on is the developer experience, how your developer is going to interact with this tool. How are they going to receive this? I think that that’s a primary driver of success in any tech space is to really focus on bringing people to this, to express things in terms that they’ll understand, and provide a good path for learning and understanding the tools. Then being able to answer questions, how do I unit test this? How do I run this locally? How long does it take for me to deploy this? How can I interact with it once it is deployed right with other things?
Swiber: Take a look at your API lifecycle, how do you go from ideation to something that’s being launched? We take a look at this in a lot of different companies. It becomes really clear, really obvious, like, our testing is lackluster over here, or the way we do authorization really isn’t all that great. I would find a place to start, and then begin bubbling that stuff up earlier in the process. Talk about security earlier in the process. Talk about testing earlier in the process, and see how that process can change because it’s not just about tooling, or what vendors can provide. Oftentimes, it’s about the people and the processes involved within the organization as well.
Gamov: Learn how to love OpenAPI spec, learn the tools that allows you to generate some artifacts out of it, regardless of the language that you use, because there’s plenty of different generators available. Learn from the API that you love to use. I learned a lot before Twitter, or before GitHub was doing GraphQL API. I learned a lot from the REST API building from just looking to their APIs and how they build their API. Look at some other APIs that are available there. There’s a Wow by Owen Wilson, every time when you watch the movie with Owen Wilson, he says, “Wow.” There’s an API that can get you the particular moment in the movie. They have OpenAPI spec that allow me to play around with this API and build some of the clients in Java and start using this in my applications. Learn OpenAPI spec and learn from the best who already implement these APIs, and you like them.
Abeysinghe: I think my advice is connected to what Matt said some time back. Basically have an outside-in approach, look at it from the consumer or the application point of view, and then come to the APIs and find whether the APIs are available. Or if you have to build it, build something that is useful for the application developers. The second thing is the thing that I highlighted about the platform. Try to find the correct platform to increase your productivity, because APIs is one part of the entire digital experiences that you are building. You need integrations, you need services, and you need identities. Try to find the correct stack that provides all these capabilities, because these are the digital core components that you need to build great digital experiences.

source

DUBLIN–(BUSINESS WIRE)–The “Enterprise Content Management System Market By Solution, By Deployment Mode, By Enterprise Size, By Industry Vertical: Global Opportunity Analysis and Industry Forecast, 2020-2030” report has been added to ResearchAndMarkets.com’s offering.

According to this report the enterprise content management system market was valued at $21.5 billion in 2020, and is estimated to reach $53.2 billion by 2030, growing at a CAGR of 9.8% from 2021 to 2030.
Enterprise content management is used to manage, capture, store, preserve, and deliver content to organizational processes. Enterprise content management reduces workload of organization by maintaining & processing the complex workflow, increase operational efficiency, and enhance customer experience. Furthermore, demand for enterprise content management system is increasing, owing to its features, including securing the stress content and integration of content with business intelligence & business analytics application.
The enterprise content management system market is expected to experience significant growth during the forecast period, owing to increase in need for digital content with the proliferation of online marketing and online customer relationship. Moreover, constant development of the e-commerce industry fuels the demand for enterprise content management systems to store, manage, create, and distribute digital content through online channels.
In addition, increase in adoption of cloud-based enterprise content management system is expected to boost the enterprise content management system market growth in the future. However, high initial costs of implementation and lack of awareness to implement the right solution for the specific needs among small and medium-sized enterprises (SMEs) hinder the growth of enterprise content management system market.
Key Benefits For Stakeholders
Key Market Segments
By Solution
By Deployment Mode
By Enterprise Size
By Industry Vertical
By Region
Key Market Players
For more information about this report visit https://www.researchandmarkets.com/r/724qq4
ResearchAndMarkets.com
Laura Wood, Senior Press Manager
press@researchandmarkets.com
For E.S.T Office Hours Call 1-917-300-0470
For U.S./ CAN Toll Free Call 1-800-526-8630
For GMT Office Hours Call +353-1-416-8900
ResearchAndMarkets.com
Laura Wood, Senior Press Manager
press@researchandmarkets.com
For E.S.T Office Hours Call 1-917-300-0470
For U.S./ CAN Toll Free Call 1-800-526-8630
For GMT Office Hours Call +353-1-416-8900

source

Nov 1, 2022

Solution Architect
Our client is is a Microsoft Gold Partner that develops Enterprise Business Applications using predominantly the Microsoft stack. Our expertise extends to System Integration, Database Development and Business Intelligence Solutions.
Duties & Responsibilities
We are looking for a Solutions Architect to join our team on an existing project. The job is either a six-month contract or a permanent placement.
The immediate need is for a solution architect for a project to deliver a comprehensive solution with the following components and technology stack:
Role, Background and Experience
You will be responsible for the overall design and delivery of this entire solution ensuring that it is fit for purpose and meets the business requirements. The overall solution design, ensuring that everything fits together, and database design will be your responsibility.
You will be expected to write the programme or module specifications for the programmers.
You will be a critical part of scrum planning and daily standups.
You will be supported by a full-time project manager, scrum master, DBA and a team of developers.
You will also be supported by a senior solution architect who has detailed knowledge of the solution.
You should have:
You do not need to have detailed technical knowledge of the software as you will not be expected to do any programming – maybe some database work such as developing suitable views or queries to assist the programmers.

Desired Skills:
Learn more/Apply for this position
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Notify me of follow-up comments by email.
Notify me of new posts by email.

Designed by Elegant Themes | Powered by WordPress

source