Co-Fields In Other Scenarios Sample Clauses

Co-Fields In Other Scenarios. The problem of coordinating the movements of a group agents has lots of in- teresting applications in several scenarios. Let us consider the exemplary per- vasive computing problem of tourists visiting a museum assisted by personal digital assistants. Specifically, we can focus on how tourists can be supported in coordinating their movements with other, possible unknown, tourists. Such co- ordination activities may include scheduling attendance at specific exhibitions, having a group of students split in the museum according to teacher-specific laws, helping a tourist to avoid crowd or queues, letting a group of tourist to meet together at a suitable location, and even helping to escape accordingly to specific emergency evacuation plans. To apply the Co-Fields model to this scenario, we need a computer infrastruc- ture suitable in supporting fields propagation across the museum. Specifically, we can suppose that the museum is provided with an adequate embedded com- puter network. In particular, embedded in the museum walls (either associated to each artistic items or to each museum room), there will be a network of com- puter hosts, each capable of communicating with each other and with the mobile devices located in its proximity via the use of a short-range wireless link. The number of the embedded hosts and the topology of the network may depend on the museum, but the basic requirement is that the network topology mimics the topology of the museum plan (i.e. no network links between physical barriers, like walls). On each host there will be a middleware providing basic support for data storing (to store field values) and communication mechanisms (to prop- agate fields) [13]. Moreover, we can suppose that tourists are provided with a software agent running on some wireless handheld device, like a palm computer or a cellular phone, in charge of giving her/him suggestions on where to move. Devices connect to nearby embedded hosts (to this end some kind of lo- calization mechanism has to be enforced [2]). They can inject fields across the network and read field values in the neighborhood to enforce field-based coor- dination (e.g. move to the room where the gradient of a field goes downhill). With this regard, it is worth noting that the critical assumption made about the museum network topology is about not having people stumbling at walls while following gradients. More details on this Co-Fields application can be found in [12]. The above scenario and the ...
AutoNDA by SimpleDocs

Related to Co-Fields In Other Scenarios

  • Pesticide Prohibition Tenant shall comply with the provisions of Section 308 of Chapter 3 of the San Francisco Environment Code (the “Pesticide Ordinance”) which (i) prohibit the use of certain pesticides on City property, (ii) require the posting of certain notices and the maintenance of certain records regarding pesticide usage and (iii) require Tenant to submit to the Airport an integrated pest management (“IPM”) plan that (a) lists, to the extent reasonably possible, the types and estimated quantities of pesticides that Tenant may need to apply to the Premises during the terms of this Lease,

  • Software Casos de Uso Red Hat Enterprise Linux Desktop Red Hat Enterprise Linux Workstation Sistemas de computadoras personales con el fin principal de ejecutar aplicaciones y/o servicios para un usuario único que por lo general trabaja con una conexión directa al teclado y la pantalla. Nota: La implantación de autorizaciones asociadas de sistema Red Hat Network o Módulos de Gestión Inteligente en un sistema que no sea Red Hat Enterprise Linux Desktop o Workstation no es un Caso de Uso soportado.

  • Sugar-Sweetened Beverage Prohibition Contractor agrees that it shall not sell, provide, or otherwise distribute Sugar-Sweetened Beverages, as defined by San Francisco Administrative Code Chapter 101, as part of its performance of this Agreement.

  • Packaged Water Prohibition Contractor agrees that it shall not sell, provide, or otherwise distribute Packaged Water, as defined by San Francisco Environment Code Chapter 24, as part of its performance of this Agreement.

  • DIRECT ORDERING WITHOUT A FURTHER COMPETITION 2.1 Subject to paragraph 1.2 above any Contracting Body ordering the Services under this Framework Agreement without holding a further competition shall:

  • Placement of DNS probes Probes for measuring DNS parameters shall be placed as near as possible to the DNS resolvers on the networks with the most users across the different geographic regions; care shall be taken not to deploy probes behind high propagation-­‐delay links, such as satellite links.

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • Advertising Prohibition Provider is prohibited from using Student Data to (a) market or advertise to students or families/guardians; (b) inform, influence, or enable marketing or advertising efforts by a Provider; (c) develop a profile of a student, family member/guardian or group, for any commercial purpose other than providing the Service to Client; or (d) use the Student Data for the development of commercial products or services, other than as necessary to provide the Service to Client.

  • Smoking Prohibited As a public school, the School shall prohibit the use of tobacco at its school or at School functions.

  • Third-Party Offerings Dell may offer Third-Party Products for use with the APEX Service through an online marketplace, or using Dell’s then-current Third-Party Product resale programs (e.g. “Extended Technologies Complete”, “Software & Peripherals (S&P)”). Third-Party Products that Distributor orders from Dell through these resale programs are referred to as “Third-Party Offerings”. Distributor may offer Third-Party Offerings to Reseller to offer to Customer for Customer’s use, at Distributor’s option, if available. If Distributor chooses to offer Third-Party Offerings to Reseller for Reseller to offer to Customer for Customer’s use, Distributor, Reseller, and Customer are responsible for complying with any terms applicable to the Third-Party Offerings, including any separate fees imposed by the provider of that Third-Party Offering (whether payable to Dell or directly to the third-party provider). Distributor agrees to comply with the standard license, services, warranty, indemnity, and support terms of the third-party manufacturer/supplier (or an applicable direct agreement between Distributor and the third-party manufacturer/supplier) for the Third Party Offering. Even if Dell invoices for them, Dell does not provide support services for Third-Party Offerings. Distributor must contact the applicable third-party directly for support. Third-Party Offerings are provided “AS IS”. Any warranty, damages or indemnity claims against Dell for Third-Party Offerings are expressly excluded. Dell may suspend or terminate provision and hosting of any Third- Party Offerings at any time, and that suspension or termination will not be deemed a material change to the APEX Service for the purpose of Clause 3.2 (Material Modifications).

Time is Money Join Law Insider Premium to draft better contracts faster.