Service Portability Sample Clauses
POPULAR SAMPLE Copied 1 times
Service Portability. DAPSI encourages proposals that aim to create (or enhance) viable open alternatives for widely used proprietary services that limit our freedom to move: whether it is online conferencing tools like Google Hangouts, Skype or WhatsApp, online office applications, social networks, software repositories, online calendars, platforms like Salesforce, etc. A project can be a new project, but it can also build on top of upcoming open alternatives for these consumer and business services – such as Peertube, Pixelfed, Jitsi, Etebase, the XMPP ecosystem, OpenStreetMap etc. that can be extended. Since make switching easy is crucial, adding "Import from ..." functionality from widely used proprietary services in these projects can also help to make data and portability be a more satisfying experience. Due to the limited time of participation in DAPSI, projects under this category can create a first version as catalyst for future work of the community or improve existing works in the field. data and migrating data whenever and wherever it is desirable. It is the key enabler to move from services to services, e.g., it is important that individuals have the freedom to choose which parts of data to share and transfer (instead of being forced to an all-or-nothing approach). Self-sovereignty of individuals data and capacity for selective disclosure is a practical use case that is also the key focus of EU regulatory efforts associated with proposed amendments to the eIDAS regulation and introduction of EU digital identity passports. Beyond the basic technology infrastructure of digital credentials, etc, to promote uptake by mainstream industries, it is important that more business use cases are developed that reinforce and demonstrate the value of managing data disclosure in this way. Please, note that DAPSI is not looking for only blockchain-based ideas. Data sovereignty is a much broader concept than blockchain. The proposals that only address the blockchain aspect of Data sovereignty are not the target of DAPSI.
Service Portability an employee transferred from the sending Employer to the receiving Employer will port her/his service and service-related banks to the receiving Employer;
Service Portability. Both parties agree that due to the dynamic nature of Dial Access Internet traffic, it is their intent to allow portability of the Ports to different locations. Reasonable re-allocation of Ports between LCAs that are serviced by a single physical Pac-West location shall be accommodated without charge. In the event of a re-allocation of Ports between LCAs that are serviced by different physical Pac-West locations, the parties agree to negotiate in good faith with regard to timeframes and the one-time non-recurring costs, which shall be limited to reasonable time and materials, for such portability.
Service Portability. DAPSI encourages proposals that aim to create (or enhance) viable open alternatives for widely used proprietary services that limit our freedom to move: whether it is online conferencing tools like Google Hangouts, Skype or WhatsApp, online office applications, social networks, software repositories, online calendars, platforms like Salesforce, etc. A project can be a new project, but it can also build on top of upcoming open alternatives for these consumer and business services – such as Peertube, Pixelfed, Jitsi, Etebase, the XMPP ecosystem, OpenStreetMap etc. that can be extended. Since make switching easy is crucial, adding "Import from ..." functionality from widely used proprietary services in these projects can also help to make data and portability be a more satisfying experience. Due to the limited time of participation in DAPSI, projects under this category can create a first version as catalyst for future work of the community or improve existing works in the field. enable individuals to control their personal data and use it to their benefits. This sub- domain is therefore dedicated to the development of specific methods and tools that transfer users’ data from one environment to another with as little effort as possible. The FAIR1 principles, as well as syntactic and semantic interoperability, must be taken into account here. Solutions should also make use of open technologies, common shared formats, structures, and standards, where applicable. If it becomes necessary to develop a new standard, this must be well argued. It must be ensured that the standard-setting process involves relevant stakeholders and standardization committees and is efficient at the same time. A clear high-level definition is necessary. Possible areas and aspects of work are the following (a combination is also welcome): • Implementations featuring researched and evaluated models for interoperability, allowed open formats and open specifications of domain- specific data structures (e.g. a catalogue of basic standards and tools to transform between them). • Design and develop standardized vocabularies and ontologies describing relevant domains and their exploitation to structure personal data in order to facilitate data transfer without giving away company secrets or violating legal duties and obligations (taking already available GRPR-compliant efforts in developing data privacy vocabularies into account). • Tools or methods for semi-automatically converting data from o...