Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hello Everyone! Exciting news! We're hosting Impact 2024, Cognite’s first User Conference, and we want YOUR use cases to shine. You can read more about Impact 2024 here. Why Share your Use Case?Your stories inspire. Share how your projects have driven real business impact, from boosting revenue to streamlining processes. We also welcome discussions on challenges you've faced and unresolved issues. This can spark meaningful conversations and potential solutions during the event.How to Get Involved:Submit your use case in this thread including it's impact. Based on the submissions, we will organize workshops to explore these use cases further. If your use case is selected, you will receive a free ticket to Impact 2024. We are committed to fostering a collaborative environment while respecting confidentiality and competition concerns, ensuring we all become better together. Mark Your Calendars:Submissions Open: April 25, 2024Submission Deadline: June 1, 2024Winners Announced: August 1, 20
Hi, my name is Geir Engdahl and I’m co-founder and CTO of Cognite. Cognite is currently considering a new mechanism for API versioning for the CDF API. What are your thoughts on this proposed mechanism? I am very eager to hear your input! Why The goal of this mechanism is to: Make it easier to make smaller breaking (ie. non backwards-compatible) changes to the API Allow us to run multiple versions of the API in parallel Avoid unexpected breakages for API clients Make upgrading version as easy as possible for API clients Be backwards compatible so no existing clients break An example of a breaking change could be to introduce a cleaner structure in the JSON request body for a particular query endpoint, e.g by replacing a previous string field with a nested JSON object. How to Our preferred method of accomplishing this is with a new API header, cdf-version, which takes the format YYYYMMDD and fixes an API client to the API as of that date. We consider this version as a major vers
When we founded Cognite four years ago, one of the success criteria we envisioned was that a developer should be able to write a useful industrial application within one hour of being onboarded to Cognite Data Fusion. Coming from the consumer software industry, we did not quite realize how ambitious that was until later. Just think of what it was like to write a mobile phone application 15 years ago. There was no iOS or Android. If you were lucky, you would be writing custom J2ME code for each handset. And there were thousands of different ones, all doing things differently. Fast forward to today, and it is possible for a committed developer to write and distribute a mobile application that runs on most smartphones in the world in a weekend. The industrial world has a similar fragmentation issue that Android and iOS addressed a decade ago. Hundreds of different OT (Operational Technology) systems are present even within a single mid-sized industrial company. They do things slightly dif
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.