Why are we doing this?
Presently it is hard to access data across higher education. Data interchange standards are not widely implemented by vendors, academic institutions, and government agencies. Where standards are implemented they are not registered or documented in an infrastructure that allows them to be readily used by people building integrations and looking for data. EdUnify infrastructure will allow vendors, academic institutions, and government agencies to register their data interchange specifications and implementations and map them to standard terminology for interoperability. Users of EdUnify will be able to use this registry and vocabulary services to build integrations, inventory services, and access data across higher education. PESC is the right organization to undertake this effort, because it is a neutral party with a track record of success in developing and implementing standards.
For a list of Task Force members and contact information, see the PESC EdUnify Task Force Participants page. To enroll other participants contact Michael Sessa, PESC Executive Director, at email@example.com.
What is EdUnify?
We are presently gathering requirements and considering candidate technical architectures and design. However, it is important to put some stakes in the ground and say what we know or what we think we know in order to have a productive discussion about what EdUnify will be and what applications we can build using EdUnify once it exists. At this phase of the project, we are constantly gathering more requirements and reviewing the design in light of those requirements. However, presently believe EdUnify will be:
- A web service registry or index with a suite of applications built on top of that registry or index.
- Web service search implemented as a web application interface for human interaction with the registry or index and a web service interface for programmatic searches of the registry or index. The search service may be free, a chargeable service, or some combination thereof based on the requirements of the business model. For example, a simple search may be free, but semantic query tools and functionality might require a fee.
- Web service search management and notification, which provides users with a means to specify and manage their searches of the registry or index over time.
- EdUnify interoperability services help users annotate web services definitions with common ontologies, so that EdUnify can apply reasoning to infer equivalencies between web services and perhaps mediate in federated queries of multiple web services.
- EdUnify feedback and rating services allow users of web services to provide feedback on the quality of the design and performance of web services. This provides valuable feedback to the developers and administrators of web services and generates more metadata for the EdUnify web service registry or index. As web services are rated, user may search for web services by quality of design and service level ratings in addition to searching by publisher and function.
- EdUnify monitoring services monitor web services that are designed to be monitored for availability by independent third parties. For example, if the publisher of a web service provides target service level information and details of how to monitor their web service in their service publication feed, EdUnify can monitor that service for availability, present that data to users, and measure the availability of the service against the target service level. These operations provide a valuable service to the web service provider (independent verification of service level) and this process generates more metadata about the service for the registry or index. Users may search for service by service level and performance in addition to publisher, function, data, user feedback and ratings.
Future Killer Applications for EdUnify
EdUnify is just infrastructure that will enable many new killer applications. This is a list of such applications. More a complete list see the EdUnify Killer Apps page.
How to Help
- Technical work group has started posting candidate technical designs from January, 29.
- Technical work group posts notes and assignments from January 15, 2010 meeting.
- Technical work group start distributed, federated directory literature survey. Please visit and contribute to the bibliography page .
- Example of the applications such infrastructure can enable,
- Questions, Questions, Questions FAQ Frequently Asked Questions
- Planning the agenda for the inaugural meeting - December 4, 2009
- Use case template and use case background posted - December 3, 2009
- Initial functional goals posted (see this page below) - November 17, 2009
- Wiki, distribution list, and Subversion repository available - November 10, 2009
- Glossary and Acronyms
We often view external challenges outside the boundaries of our organizations as out of scope, out of reach and not something we can or should focus on. Assumptions are drawn and acceptance of the current state of affairs continues.
Innovation and progress is the push to do better, improve things over the status quo. Innovation does not happen in a vacuum. It takes effort. First, we need people to step up and challenge the status quo, question the methods and look to see if there are ways to overcome the challenges and assumptions. Second, we need to explore how our community can work together through our differences, to compromise and set the stage for progress. Third, we need to realize progress is incremental. Not everything has to be addressed all at once. And finally, we need to apply our efforts to a vision that we can share, that will address our individual circumstances and how the potential effort can help us achieve great things together.
Before going too deep into EdUnify, think about your use of email today and how easy it is for you to send and receive email. It does not matter which email program you utilize, the interchange works the same. Who, how and when did we establish the convention of firstname.lastname@example.org? How do we register domain names like academyone.com or emory.edu? How does the computer program I use, reference and send my email and how does my email get to my destinations without someone lifting a hand? And, how did the @ sign become the separator? These 'standards' reflect solutions and decisions made just few short years ago that has made email computing services simpler to use and transparent. Adoption and compromise are voluntary decisions. There was no law passed. There was no decree from government.
We can learn alot by understanding the evolutionary path of email. What came first, the demand? Or, the innovation? How did a community come together to face the challenges of exchanging electronic messages? There were plenty of vendor products routing messages. How can we learn from the path taken by early ventures to bridge email systems? As they came together to address their differences, with similar set of challenges, how did they compromise? How did they adapt? Moving or accessing electronic data, in what ever form it is in, from program to program, place to place, across computers is complex. How did they reduce the complexity, obstacles and legacy of doing it my way?
Then, ponder how easy it is to travel by car north and south or east and west across state lines and towns across America. We have a system of roads we mostly take for granted today. Imagine what it would be like getting in your car and driving to the store five miles down a dirt path? Or, that we had roads, but their were no standards on how to travel on them, like which side do you drive on, or what do the signs mean along the way? On many toll roads, we now have Ezpass, a device put on your windshield that can be read from toll booths while traveling 35 MPH. It eliminates stopping, wasting gas and time. It consolidates monthly billing for tolls. It works on many highways and even parking garages. It is simple to establish one account that works across many States. And, it does not add costs to the trip.
In our recent memories, events often collapse and we forget about how difficult it was prior to let's say Google or the Cell Phone. How did we search for information in the 50's, 60's, 70's and 80's? What happened to card catalog files and the augmentation of libraries sharing their repositories that began in the 70's indexing holdings? Or, what was life like before Amazon or Facebook for many younger today. Do you recall Gopher, Compuserve or BackRub? Collaborative efforts can realize great results. Read more about three major technology innovations and collaborations born by a few people who came together to change our world for the better. They decided to overcome the challenges and invest in developing ideas that could bridge frontiers thought overwhelming. Not only did they change the face of America, they improved how we live and work reducing the distances and times we spend moving from place to place, either physically or virtually. Revolutionary Ideas
We are glad you have come to this wiki site. We have come together to face one of our toughest challenges haunting higher education and education efforts in general. That is, how can we overcome the inhibitors and obstacles of data access and movement, the huge costs layered within the movement and exchange of data across computer applications to foster new tools and methods to address the challenges of research, teaching and learning in the 21st century, which is not bound by border, physical or otherwise.
Statement of the Problem
Across education, the utilization and effectiveness of data and information technologies is severely inhibited by access methods, differing protocols, non-standard payloads, varying data definitions, and inability to trust disparate applications stove piped by proprietary design. Billions of dollars are spent annually trying to move data across components employed by stakeholder computer systems. The current state of automation, with all its redundancy, unnecessary aggregation and inaccuracy render a tremendous burden on the educational investment society as a whole is making.
Policy, governance, research, teaching, administration, funding, and learning are all impacted. The unintended consequence of metered design without considering the external interchanges which contribute to additional obstacles and costs is avoidable. The accurate, authoritative and secure transmission of data spanning components and stakeholders would respect and reinforce autonomy and roles, by connection, rather than push the work around mentality that has been fostered by the industry fearful of data access, use and security.
The education industry spends approximately 4% of operating expenses on IT which approximates $50 Billion annually. Of that, approximately 50% or $25 Billion is spent supporting connections and movement of data across disparate applications inside and outside the institution poorly. Even with that much money spent to keep things band-aided together where funding has been applied, the ineffective use of technology is wasting away the capacity of tools and the investment in automation. Without addressing the challenge to bridge systems and components, we will be continually haunted by what could be, rather than what is. Automation can empower and serve the industry with innovation and unity in purpose. Thus, the call for EdUnify, to create a registry, lookup, and supporting services to enable applications and computer systems to seek and connect through a common abstract pipe following community developed methods, protocols, payloads and services promoted on a voluntary basis.
What is EdUnify?
EdUnify is a set of core services enabling the universal registration, lookup, and invocation of web services and other forms of data exchange allowing clients to find, access, and secure data exchange calls. EdUnify will address deployed, implemented, and abstract services. Deployed services are those that are operational and can be accessed on the web. Implemented services have been defined and implemented, but are not deployed and operational. Abstract services are typically either specifications or designs. Abstract services may or may not have implementations at any point in time. The high-level goals of EdUnify are:
- positively impact the business of teaching, research and learning.
- open access to a directory of registered services distributed across stakeholders.
- protect access to secure services and data thru a trusted network of registrars servicing registrants.
- leveraging existing standards technologies, tools and applications.
- enable development of new technologies, tools and applications.
- enable data to be used in new ways and increase the value of data.
- economic sustainability of EdUnify
- enable the connection of disparate systems, applications and technologies.
- abstraction of services to buffer physical properties underlying data sources.
- utilize a common framework, protocols and semantics accepted by industry stakeholders.
- advertising the stakeholder services reinforcing reuse.
- save us money, save us time, improve customer service.
- provide the opportunity for new business models, revenue generation.
The specific technical goals of the task force are:
- document use cases that articulate our goals.
- develop a plan to design a registry with metadata about web services.
- enable integration, ontology, data exchange services.
- develop a registration and maintenance processes that make sense for education.
- prove the concept with reference implementations among participating organizations.
- stimulating the publication and use of existing access methods
- stimulating new access method specifications through PESC, SIFA, IMS or other standard bodies.
- drive adoption within our organizations.
Functional Goals and Epic Stories
The following are examples of potential high-level functional goals.
- Respect the federation and automony of information service providers who have their own interests to design, develop, deploy and maintain data and analytic systems with different data stores across education enterprises.
- Provide fast, reliable and secure access to a federated Registry and Lookup Services to improve people's productivity through applications designed to channel request for services and response to service requests abstracting the differences in data and methods behind them.
- Enable the PESC and SIFA community to foster sharing of data and method (functions) reuse across stakeholder applications, utilzing direct and indirect automated bridges.
- Enable the development of alerts and feedback loops across the P20 landscape without imposing or forcing how, by letting the open marketplace and motives to drive improvement in services through collabortive technologies.
- Respect organization controls, business policies and practices over their data and services.
- Enable people and organizations to align initiatives, improve outcomes and reduce duplication dispersed across information technology investments reducing the tax imposed by integration and interface complexity.
- Allow everyone to gain access to data definitions, semantics and enumeration which will improve how services are developed and delivered to people thru online applications.
- Create an extendable platform to explore, interrogate and request advertised services by stakeholder honoring the protocols, business rules and requirements managed by providers of the advertised data services.
- Build, deploy and extend a commericially profitable online marketplace to foster competition, innovation and the abstraction of proprietary interests amoung stakeholders reducing their risks, fears and anxieties inhibiting their efforts to leverage common specifications for data and methods.
The following are examples of enumerated types of services:
- Student and Faculty Data Services
- Institutional and Academic Data Services
- Course and Program Transferability Disclosure Services
- 21st Century Learners Spanning Multiple Institution Services
- Student Access to their Data through Electronic Services
- Enabling New and Innovative Technologies to Support Teaching and Learning Services
The Task Force is preparing very specific, structured use cases that the EdUnify frameworks will support to help identify specifications and technology it will develop or apply. The Task Force is preparing a set of use cases in a common format to help identify the constituents served and processes addressed in each use case. There is a template which can be used to start each new use case. For more details visit the Use Case page.
- EdUnify Use Cases
- EdUnify Directory Services Bibliography
- EdUnify Subversion Repository
- EdUnify Organization Efforts
- Technical Design Documentation
- Glossary and Acronyms
- EdUnify Service Publication and Discovery Architecture Discussion
Meetings/Events - Agendas
- Business Plan Work Group meets Wednesdays from 2-3 PM EST See Details
- Technical Work Group meets Fridays 2-3pm eastern time. See details.
- EdUnify Task Force Meeting December 17th-18th