Query Sample Clauses
Query format: whois “nameserver (nameserver name)”, or whois “nameserver (IP Address).” For example: whois “nameserver NS1.EXAMPLE.TLD”.
Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.
Query. Is XP a viable goal? If so, halt with “XP” as the search result
Query. For purposes of this Agreement, the Parties agree to fulfill their N-1 carrier responsibilities and perform queries on calls to telephone numbers with portable NXXs. Neither Party shall send un-queried calls to the other Party.
Query. Non-queried calls will be returned to the N-1 carrier, or logged and charged to the carrier originating the call, at the then-current LNP Query rate specified in the tariffbelonging to the Party performing the query.
Query. A Query Binding evaluates to a specified value in the data object or list of data objects returned by a query. For example, you can display a list of hosts from a selected data object. A Query has the following properties:
Query. Is a message that represents a request to a Database for information.
Query is_in_role_string (a_role: SYSTEM_STRING): BOOLEAN is -- dotnet_name: "WindowsPrincipal.IsInRole (role: String): Boolean" -- (+2 overloads) 3 An interface view is not a valid Eiffel class; it is a form of software documentation. Result := windows_principal_xxx.xx_in_role (a_role) is_in_role_windows_built_in_role (a_role: WINDOWS_BUILT_IN_ROLE): XXXXXXX is -- dotnet_name: -- "WindowsPrincipal.IsInRole (role: WindowsBuiltInRole): Boolean" -- (+2 overloads) Result := windows_principal_xxx.xx_in_role (a_role) is_in_role_integer (a_rid: INTEGER): BOOLEAN is -- dotnet_name: "WindowsPrincipal.IsInRole (role: Int32): Boolean" -- (+2 overloads) Result := windows_principal_xxx.xx_in_role (a_rid) A similar error occurs in the class System.Type which inherits from System.Reflection.ICustomAttributeProvider. The interface ICustomAttributeProvider has an overloaded feature GetCustomAttributes. In Eiffel for .NET the corresponding feature names are translated into get_custom_attributes and get_custom_attributes_type. (The Eiffel emitter4 only adapts the name of one feature; the other feature name stays the same.) This means that all Contract Wizard proxy classes inheriting from ICUSTOM_ATTRIBUTE_PROVIDER must list features with exactly the same name. The Contract Wizard does not know how the features are named in the inherited Eiffel for .NET class. It applies the standard renaming algorithm and translates the feature names into get_custom_attributes_boolean and get_custom_attriubtes_type. This particular problem could be solved when the generated Eiffel proxy classes do not inherit from the abstract classes produced by the Eiffel Emitter (e.g. ICUSTOM_ATTRIBUTE_PROVIDER), but from the according class generated by the Contract Wizard (e.g. CW_ICUSTOM_ATTRIBTE_PROVIDER). Because the class CW_ICUSTOM_ATTRIBUTE_PROVIDER contains two features with the same name, it adapts the name of both. There exist classes where it is not understandable how the Eiffel Emitter generates the names for overloaded features in wrapper classes. (The algorithm used by the Emitter is not publicly available.) Table 29 shows an example from the deferred class ITYPE_LIB_CONVERTER. The Contract Wizard does not generate the same name for the overloaded feature convert_type_lib_to_assembly in the descendant Eiffel proxy class CW_TYPE_LIB_CONVERTER and therefore the compiler prints an error message. The first
Query. Limit The number of Queries allowed for each calendar month is subject to Adverity’s Fair Use Limit, which is calculated at 50 times the monthly Subscription Fee, translated into Queries (for example, EUR/GBP/USD 3000 monthly Subscription Fee = up to 150k Queries). If Customer exceeds the said monthly Fair Use Limit, Adverity will not immediately increase Customer’s Subscription Fee or limit access to the SaaS. Adverity will evaluate Customer's requirements and assess Customer´s specific needs regularly and reserves the right to increase Fees in case of consistent overuse.
Query. Management System the online database maintained by the Supplier for registering Queries and Complaints from customers. Reasonable and Prudent Operator a person acting in good faith to perform its contractual obligations in compliance with all Applicable Laws, the Licence and Industry Documents and in so doing and in the general conduct of its undertaking, exercising that degree of care, skill, diligence, prudence and foresight which would reasonably and ordinarily be expected from a skilled and experienced material or service provider, as the case may be, engaged in the same type of operation and undertaking in the same or similar locality and under the same or similar circumstances and conditions, and any reference to the standard of a Reasonable and Prudent Operator herein shall be a reference to such degree of care, skill, diligence, prudence and foresight as aforesaid. Re-establishing the meaning given to "Re-establish" in the Uniform Network Code. Registered has the meaning given to it in the Uniform Network Code and “Registration” and “Register” shall be construed accordingly. Regulatory Bodies those government departments and regulatory, statutory and other entities, committees and bodies which, whether under statute, rules, regulations, codes of practice or otherwise, are entitled to regulate, investigate, or influence the matters dealt with in this Agreement or any other affairs of the Authority.