Data & Content. 9.1. While XDSL recognises the Customer’s right to privacy of its data, the Customer agrees that XDSL may monitor the Customer’s use of the System so as to ensure that the System is operating properly.
9.2. XDSL has no knowledge of or interest in the data transmitted to, stored on or accessed from the Co-located Equipment by the Customer, subject to the further terms of this Agreement. XDSL has moreover no duty to monitor any content made available or published through the System, subject to the provisions of clause 11.
9.3. The Customer agrees that no action shall lie against XDSL for any damages howsoever arising as a result of any act or omission relating to the transmission of data to and from the Co- located Equipment, its storage on the Co-located Equipment or its publication using the Co- located Equipment to third parties, and the Customer further indemnifies and holds XDSL harmless in respect of any action brought by a third party resulting from such acts or omissions.
Data & Content. 9.1. While STEM CONNECT recognises the Customer’s right to privacy of its data, the Customer agrees that STEM CONNECT may monitor the Customer’s use of the System so as to ensure that the System is operating properly.
9.2. STEM CONNECT has no knowledge of or interest in the data transmitted to, stored on or accessed from the Co-located Equipment by the Customer, subject to the further terms of this Agreement. STEM CONNECT has moreover no duty to monitor any content made available or published through the System, subject to the provisions of clause 11.
9.3. The Customer agrees that no action shall lie against STEM CONNECT for any damages howsoever arising as a result of any act or omission relating to the transmission of data to and from the Co-located Equipment, its storage on the Co-located Equipment or its publication using the Co-located Equipment to third parties, and the Customer further indemnifies and holds STEM CONNECT harmless in respect of any action brought by a third party resulting from such acts or omissions.
Data & Content. Except as provided in this Section, all Data is transferred to NEWGEN in AS IS, WHERE IS condition. No warranty whatsoever as to the content, condition of, or usability of the Data is made by ADP, EXCEPT THAT ADP REPRESENTS AND WARRANTS THAT IT WILL NOT INTRODUCE ANY BUGS, ERRORS, OR VIRUSES INTO THE DATA AND THAT THE DATA SUBMITTED TO NEWGEN WILL NOT BE CHANGED, ALTERED, OR MODIFIED FROM THE FORM AND CONTENT RECEIVED BY ADP, EXCEPT FOR NORMAL ADP EDITING PROCESSES AS MAY BE AGREED UPON BY ADP AND NEWGEN. ADP ALSO REPRESENTS THAT ALL DATA SHALL BE PLACED INTO THE PROPER RECORD LAYOUT. ADP DOES NOT MAKE AND NEWGEN DOES NOT RECEIVE FROM ADP ANY EXPRESS OR IMPLIED WARRANTIES OF ANY KIND WITH RESPECT TO ALL OR ANY PORTION OF THE DATA. ADP HEREBY EXPRESSLY EXCLUDES ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO THE DATA.
Data & Content. As mentioned above, a web service both requires some form of input and provides some form of output to the end user. This means that it is necessary to ensure a smooth flow of rights along with the data in the web service and to the end user. However, methodologically, we should start with the forms of data output, as this is going to define the range of rights necessary at the stage of the data input. We also need to assess the type of data processing that takes place in order to ensure again that all necessary rights have been obtained or that the legal risks have been minimized.
Data & Content. 9.1. While Digital Parks Africa recognizes the Customer’s right to privacy of its data, the Customer agrees that Digital Parks Africa may monitor the Customer’s use of the System so as to ensure that the System is operating properly.
9.2. Digital Parks Africa has no knowledge of or interest in the data transmitted to, stored on or accessed from the Collocated Equipment by the Customer, subject to the further terms of this Agreement. Digital Parks Africa has moreover no duty to monitor any content made available or published through the System, subject to the provisions of clause 11.
9.3. The Customer agrees that no action shall lie against Digital Parks Africa for any damages howsoever arising as a result of any act or omission relating to the transmission of data to and from the Collocated Equipment, its storage on the Collocated Equipment or its publication using the Collocated Equipment to third parties. The Customer further indemnifies and holds Digital Parks Africa harmless in respect of any action brought by a third party resulting from such acts or omissions, subject to the provisions of clause 11.2.
Data & Content. The data content is described by the Parameter elements. There must be one such element for every parameter present in the data files. Parameter contains: (1) a name to the parameter (Name) that tools can display; (2) a reference to the parameter name in the data files (name of the column for files in VOTable format, name of the variable for files in netCDF, CDF...); and (3) description of the physical content of the parameter in a way that can be handled by automated tools (in particular through the use of the *Quantity and Qualifier elements. For particle parameters, PopulationID identifies a given population.
Data & Content. The data generated by the pre-day simulation that feeds the EGTrain simulation consists of detailed activity and travel plans for each individual from a synthetic population according to the pre-day models estimated. For each individual, it contains: (i) daily plan of out-of-home activities (if any), as well as their location, duration and purpose, and (ii) daily plan of travels (if any), as well as the transport modes used to perform them and the time when they happen (Table 9). The data from the EGTrain simulation to the pre-day simulation consists of infor- mation on travel times and costs for traveling by rail at different time intervals during the day. This information must be aggregated into zones to be used in the pre-day simulation.
Data & Content. The interface between EGTRAIN and the route choice model allows the ex-change of two sets of information. In one direction, each passenger object in EGTRAIN may call the route-choice function at predefined triggering events. The passenger needs to pass origin, destination (stations), and (travel or re-routing) start-time to the route choice function. The latter also needs to have access to the latest RTTP. In the opposite direction, the route choice model sends the selected se- quence of trains to be taken by the passenger.
Data & Content. The interface between EGTrain and the control architecture aims at sharing two types of information. On the one hand, static information concerning the railway infrastructure, planned timetable information and rolling-stock characteristics. On the other hand, dynamic information on the traffic and demand state, and on traffic management decisions to be implemented. Static information and dynamic information on traffic and demand state are sent by EGTrain and taken as input by the control architecture. Dynamic information on traffic management decisions are sent by the control architecture and used as input by EGTrain.
Data & Content. The data sent by the control architecture to the online demand prediction module include the observed or predicted passenger state from the TSP and a train time- table. The latter is an extraction from the RTTP only including arrival and depar- ture times at station platforms. The data returned by the online demand predic- tion module to the control architecture include the information on the trips of homogeneous groups of passengers (with same origin, destination and route, and similar arrival time at the origin station).
