Graphical and multi modal query language to access information within data streams Sample Clauses

Graphical and multi modal query language to access information within data streams. There are two parts to the query language as it is offered to the end-user: the creation of data processing instances as queries over the DSMS, and the consumption of the information delivered by these queries. Hiding the complexity of the textual query language potentially limits the expressiveness for queries to be expressed. The available semantic subset of the textual query language is a function of the employed modality. To select meaningful subsets requires the identification of suitable trade-offs between expressiveness and ease of use for the different modalities and user's expertise. Similar considerations apply to the consumption of the information from the expressed queries. The different modalities and employed interaction techniques determine the dimensionality and frequency of information from the DSMS to be perceived and processed by the user with acceptable cognitive load. The visual and multi-modal query language should support the access data streams (and related metadata) for both local and remote users in various formats. It should allow users to define queries over data streams, parameterize them and create and position resulting views in the personal or shared workspace. Query building and configuration should be based on conceptualizations with a formal syntax and semantics to be matched with the syntax and semantics of the underlying textual query language. The query building environment has to provide visual and multi-modal tools that allow unskilled end-users to perform data stream queries navigate the results and mine other hidden relevant information. Graphical and multi-modal primitives, as well as basic visual and multi-modal queries, should be made available via a user query library extendable by the user by adding and storing composite queries. The environment should enable multiple combinations and compositions of conceptualizations to reflect advanced query constructs and allow users to aggregate/disaggregate, filter and browse data in order to focus on relevant information. Depending on the textual query language capabilities, visual and multi-modal query formulation tools should allow both intensional and extensional queries operating on the data stream model or their representation.
Sample 1
AutoNDA by SimpleDocs

Related to Graphical and multi modal query language to access information within data streams

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8, in accordance with, but only to the extent required by, Applicable Law, Verizon grants to CBB a non-exclusive license to use Verizon OSS Information.

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Contractor Sensitive Information 17.1 The Authority must:

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • INFORMATION AND APPLICATIONS POLICY LANGUAGE For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

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