...
What's the value of contributing code to ADAPT?
asdasdAdoption of Field Operations data by growers has lagged behind its potential for decades. To dramatically increase adoption system interoperability needs to be achieved at a dramatically reduced cost for the industry. Contributing improvements to the ADAPT framework will accelerate the industry's ability to achieve this goal!
What use cases are supported by ADAPT, and what's the roadmap?
asdasdsAgGateway's ADAPT Oversight Committee is currently working on outlining the steps required to implement a "Version 1" of ADAPT - which has a focus on documentation data generated by field computers (MICS) being consumed by business systems (FMIS).
I want to adopt ADAPT: Where do I start?
...
The developer guide and sample application cover most of the scenarios of accessing and writing data. You will need an application which can consume a .net/mono library.
- A guide on how to tackle the project, what steps make sense to do in what order as I implement connecting the whole framework and data model to the existing FMIS platform
- As a terminal manufacturer creating a plugin I would like an example of an existing plugin and some guidelines on what the plugin requirements are. It may have been a while since I really looked at a FODD or anything similar so this might be all new to the development team
What is the business case for adopting ADAPT?
lorem ipsum dolorThe ADAPT framework is focused on providing a Data Model that covers a comprehensive superset of Field Operations Data. The goal is to allow a single integration for any Farm Management Information System - FMIS and through licensing of various plugins provided by different manufacturers (of systems that produce/consume Field Operations Data) the FMIS can read/write to a wide variety of systems with little incremental effort. The scope is quite broad - beyond field computers in self propelled machines (e.g., tractors) to include irrigation control and monitoring systems (in future versions). The goal is to expand the compatibility with even more kinds of Field Operations Data going forward. As an Open Source Software project, the ADAPT Oversight Committee is focused on providing a framework that can evolve as the industry sees fit.
ADAPT is open-source software; what does this mean to me and my company?
asdasddasdADAPT has been developed under the Eclipse Public License v1.0 Equipment manufacturers desire an approach that can be used with Farm Management Information System (FMIS) companies anywhere in the world that they do business. An open source approach allows non-AgGateway member companies to leverage the framework, providing the ability to:
Modify the framework to meet their commercial needs quickly, and evolve the standard interface for everyone.
Submit modifications back for consideration to incorporate into ADAPT (which are reviewed before acceptance)
From Wikipedia: Open Source Software is “A development model (which) promotes a universal access via a free license to a product's design or blueprint, and universal redistribution of that design or blueprint, including subsequent improvements to it by anyone.”
If I Use ADAPT, which is open-source, does that mean I have to give my software away or something
...
like that?
...
ADAPT is provided under the terms of the Eclipse Public License
From Wikipedia: The Eclipse Public License is designed to be a business-friendly free software license and features weaker copyleft provisions than contemporary licenses such as the GNU General Public License (GPL).[7] The receiver of EPL-licensed programs can use, modify, copy and distribute the work and modified versions, in some cases being obligated to release their own changes.[8] The EPL is approved by the Open Source Initiative (OSI)[3] and is listed as a free software license by the Free Software Foundation(FSF).[2]
ADAPT Model Questions
Are there any tools to help me understand the object model?
...
Is ADAPT a Data Transfer Tool?
asdasdasdADAPT is not focused on data transmission, instead it is focused on data translation/conversion. This is not to say a plugin provider won't put a mechanism in their plugin which enables data transmission (upon use of the plugin) to a specific "cloud service." It is important for the companies that license a specific plugin to know the terms which they agree to.
Is ADAPT an API? An SDK?
asddADAPT consists of two main components.
- ADAPT Framework - The Software Development Kit that includes the data model, APIs and other tools which can be integrated into FMIS systems under AgGateway licensing terms.
2. ADAPT Framework Plugin - a data converter for a specific data format which can be easily integrated into a specific data format which can be easily integrated into a specific instance of ADAPT. A specific plugin would be created/licensed by i) AgGateway, ii) equipment manufacturers, iii) entities (e.g., USDA), iv) FMIS companies, v) individuals, etc.
When will ADAPT be done?
Can my developers start using it now?
...