GOVERNMENT OF INDIA
English language

Home | MyGov

Accessibility
Accessibility Tools
Color Adjustment
Text Size
Navigation Adjustment
Screen Reader iconScreen Reader
Menus
Sticky Menu

Policy on Collaborative Application development by Opening the source code of Applications

Policy on Collaborative Application development by Opening the source code of Applications
Start Date :
Jan 01, 2015
Last Date :
Nov 30, 2014
04:15 AM IST (GMT +5.30 Hrs)
Submission Closed

The Policy on Collaborative Application development by Opening the source code of Applications intends to increase the pace of application development and rapid roll out/ ...

The Policy on Collaborative Application development by Opening the source code of Applications intends to increase the pace of application development and rapid roll out/ implementation by adopting the principles of open-source development model. Government wants to promote reuse of existing developed applications. Successful running applications and new applications are envisaged to be developed within the public domain by opening the application source code and it is also intended to encourage innovation inside and outside Government by encouraging collaborative development to achieve better products in less time.

e-Gov application source open approach—including the use and release of application source to public—can reduce costs, reduce development time, and improve overall quality, including security through increased transparency and mass peer review.

We invite your attention and comments on the Policy on Collaborative Application development by Opening the source code of Applications

Last date for sending your suggestions is 30th November 2014.

Reset
Showing 3388 Submission(s)
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
COMMON POLICIES While the policy system used by Intermezzo is flexible and powerful enough to capture a range of specific and complex “real world” situations, it is also useful for describing a number of common general policies. contd..
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
Most systems that use roles have a few characteristics in common: • The set of roles in use is determined a priori by the application or environment. • The membership of those roles is typically determined early in the lifetime of the session. • Membership of a role is specified in terms of users. • There are few (if any) changes to role membership during the course of the session. contd..
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
Traditional Roles Most systems that use roles have a few characteristics in common: • The set of roles in use is determined a priori by the application or environment. • The membership of those roles is typically determined early in the lifetime of the session. • Membership of a role is specified in terms of users. • There are few (if any) changes to role membership during the course of the session. contd..
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
ROLES IN INTERMEZZO Policies are typically applied to sets or classifications of users. As noted earlier, the literature has adopted the term role to indicate a particular category of users with a set of access control rights applied to them, and in fact many Collaborative systems have found the notion of roles useful for specifying how policies are assigned to users. Intermezzo adopts the terminology of roles and applies the concept in a new direction. This section describes how policies are ap
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
THE INTERMEZZO FRAMEWORK Our policy system is built atop the Intermezzo collaborative infrastructure. Intermezzo provides coordination support to applications in the form of session management, awareness, and policy control. The system provides a foundation object model on top of which higher-level collaborative functionality is based. While this paper does not describe all the features of the Intermezzo environment, a high-level view is important for understanding how policy is implemented in I
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
The Importance of Context By examining the policy scenarios outlined earlier, we can see that many share one trait in common: they are based on information about the context of the user and the task in both the “real” world and the computer-mediated virtual world. This should not be surprising: all work, even computer based work, takes place in a physical workplace with its own demands on our time and attention. Collaboration in particular, with its reliance on “out of band” communication channe
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
The Importance of Fluidity ...users should be allowed to take multiple roles simultaneously. For instance, a teaching assistant should be able to simultaneously take the roles of “student” and “lecturer.”...It should be possible to dynamically change collaboration rights, roles, owners, and ownership semantics. This requirement allows, for instance, a user of a code inspection tool to graduate from an “observer” to an “annotator.”...access control must be performed flexibly in the ways described
Dislike (0)
Reply
Report Spam
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
The Importance of Expressiveness What work has been done to-date in policy systems for collaborative applications? Research on policy can be broadly divided into “coordination domain” policy—policy controlling between-application information, such as awareness and location information—and “application domain” policy—policy controlling application-specific data, such as access to text in a shared editor. contd..
Dislike (0)
Reply
Report Spam
Sticky Menu