The query attempts to match the triples of the graph pattern to the model.
这个查询试图把图形模式的三元模式和模型进行匹配。
This internal representation is performed by the query graph model (QGM) component.
这个内部表现形式是由查询图形模型(QGM)组件所执行的。
In such a case, the graph pattern is applied to each of the named graphs available to the query.
在这种情况下，图形模式被应用到查询可以使用的每个命名图中。
The rest of this section takes you through the access path graph one more time from the data flow perspective so that you can gain a full understanding of the performance aspect of query execution.
本节的其余部分再一次以数据流的观点向您介绍访问路径图以便您可以在查询执行的性能方面获得充分的理解。
This allows a graph to be passed to the query when it is executed.
这样就可以允许在执行查询的时候才把图传递给它。
Client applications can query a DAS and get a data graph in response, modify the data graph and send the updated data graph to a DAS to have the changes applied to the original data source.
客户机应用程序可以查询DAS并得到数据图表作为响应，修改数据图表并向DAS发送更新的数据图表，以便将这些更改应用到原始数据源中。
The first part of the query finds the node that represents me in the FOAF file, and then finds the names of the people that the graph says I know.
查询的第一部分找到了FOAF文件中代表我的那些节点，然后找到了图中描述的、我认识的那些人的名字。
Each matching binding of the graph pattern's variables to the model's nodes becomes a query solution, and the values of the variables named in the SELECT clause become part of the query results.
将每个图形模式变量的绑定与模型节点进行匹配就成为一种查询解决方案，而select子句中指定的变量值则成为查询结果的一部分。
Although not shown in the previous example, you could have defined "filter arguments" (similar to simple SQL query predicates) to restrict the rows returned for this graph.
虽然前面的例子中没有显示，但您可能定义了“筛选参数”(类似于示例SQL查询谓词)来限制为此图返回的行。
Suppose you want to write a query that returns the name of every person described by the graph in Listing 5, along with a link to a photograph for each, if one's available.
假设您想编写一个查询，返回清单5的图中所描述的每个人的名字，以及每个人的照片的链接(如果有照片的话)。
Some also require query capabilities to identify parts of the data graph.
有些应用程序还需要查询功能，以标识数据图表的某些部分。
DB2 automatically increases the database Shared memory (graph on the left) to satisfy the demands of the workload, resulting in a corresponding increase in query throughput (graph on the right).
DB 2自动增加数据库共享内存(左侧的图)以满足工作负载的需求，最终导致查询吞吐量增加(右侧的图)。
It includes how to understand the problem query better by using the visual AIDS provided by query formatting, annotation, reports, and the access plan graph.
其中包含如何通过使用查询格式化、注释、报告和访问计划图来更好地理解问题查询。
The change summary API allows you to query the Settings of all the objects in your graph and assess whether they have been changed or not.
更改摘要API允许查询图中的所有对象的设置，并确定是否已经对其进行了更改。
As with the background graph, named graphs can be specified within the query itself, using FROM named, where URI specifies the graph.
与后台图一样，命名图可以在查询内部用FROMNAMED指定，在这里，是通过uri来指定图。
From the access plan graph, you can see what choices the optimizer has made regarding how the query will be processed and the rationale for those choices.
从这张访问计划图中，您可以看到优化器对如何处理查询作出何种选择以及理由。
In addition to the background graph, SPARQL can query any number of named graphs.
除了后台图，SPARQL还能查询任意数量的命名图。
However, the query needs to be run from the directory containing the graph, because it is specified using a relative URL in the query's from clause.
但是，查询需要在包含图的目录中运行，因为该图是在查询的from子句中用相对url指定的。
Listing 11's graph clause matches on each person node in the named FOAF graphs given to the query.
清单11的graph子句和提供给查询的命名图中的每个人员节点匹配。
An access path graph not only describes the "operational details" of query execution, it also describes how the data flows.
访问路径图不但描述“操作细节”，而且描述数据如何流动。
The description of each operation includes a Query Tuner access path graph that explains its operational semantics.
每一个操作的描述都包括一个解释其操作语义的QueryTuner访问路径图。
Named graphs are used within a SPARQL query with the graph keyword, in conjunction with either a graph URI or a variable name.
在SPARQL查询内部用GRAPH关键字调用命名图，后面是图的URI或变量名。
The SQL statement in Listing 2 creates the access path graph shown on the right side of the Optim Query Tuner screenshot in Figure 2.
清单2中的sql语句创建如图2上的OptimQueryTuner截图右侧所示的访问路径图。
Table 1 describes the input, output, and function of several operation nodes that typically appear in an Optim Query Tuner access path graph.
表1描述通常出现在OptimQueryTuner访问路径图上的输入、输出和几个操作节点的功能。
A SELECT query whose graph pattern included foaf: depiction would only find three solutions.
在foaf：depiction中包含的图形模式的SELECT查询可能只会发现三个结果。
An index scan is typically shown in Query Tuner as a group of four nodes in the access path graph.
在访问路径图中，一个索引扫描通常作为一组四个节点显示在QueryTuner上。
Expression language - Spring.NET provides an Expression language which can be used at runtime to query and manipulate an object graph.
表达式语言——Spring.NET提供了一个表达式语言，可在运行期查询并操纵对象图。
Because the query USES the FROM keyword to specify the graph to use, it is necessary only to provide the location of the query file to the sparql command.
因为查询使用FROM关键字指定要使用的图，所以只需把查询文件的位置提供给sparql命令行即可。
Figure 6 is the access path graph generated by query Tuner for the sample query in this article.
图6是QueryTuner为本文中大的查询样例生成的访问路径图。
In Listing 3, you query for the foaf:phone, but a new graph is constructed with a different predicate in its place (wingerz:officephone).
清单中查询foaf:phone，不过在它的位置使用不同的谓词构造了一个新的图（wingerz:officephone）。
应用推荐