在上面的第一个可行域中，优化解决方案是解析空间中的右顶点。
In the first feasible region above, the optimal solution is the right vertex of the solution space.
注意，这个解析空间更小。
这样解析空间更小了。
正如我们给出的约束一样，这个无限的解析空间达到了边界。
As the constraints were written, this unlimited solution space gained boundaries.
这个解析空间包含了(x 1,x2)在第一象限的所有可能值，它们可以满足修整工时约束。
The solution space contains all the possible (x1, x2) solutions in the first quadrant that satisfy the finishing hours constraint.
然而，我们需要注意这个解析空间仍然是无限的(这依然可能成为我希望移居Caribbean的一种情况！)
Note, however, that this solution space is still infinite (that would be a situation in which I'd move to the Caribbean!)
在上面的第一个可行域中，优化解决方案是解析空间中的右顶点，而这个解析空间是一个由所有约束构成的三角形。
In the first feasible region above, the optimal solution is the right vertex of the solution space, which is a triangle made by all the constraints.
解析的类型取决于名称空间条目的类型。
The type of resolution depends on the type of the name space entry.
XML解析花费的时间最长，使用的空间最大。
解析时间和空间与消息格式(结构和编码)有关。
The parsing time and space is related to the format (structure and encoding) of a message.
设置关于这个解析器或转换器的配置选项（验证、名称空间感知、要使用的样式表等等）。
Set configuration options on or around that parser or transformer (validation, namespace-awareness, stylesheet to use, and so on).
如果解析器已经知道命名空间中的模式类型，或者有其他寻找这些模式类型的方法，它就不需要定位到你所提供的位置。
If the parser already knows about the schema types in that namespace, or has some other means of finding them, it does not have to go to the location you gave it.
为了与SAXAPI一致，解析器必须遍历所有的属性来删除名称空间声明，即使在起始标签中没有指定名称空间声明，它也会这样做。
In order to conform to the SAX API, the parser must iterate over the set of attributes to remove any namespace declarations, even when no namespace declarations have been specified on the start tag.
假设需要规定解析器从哪里查找具有特定目标名称空间的模式文档。
Suppose you want to specify where the parser looks to find schema documents with particular target namespaces.
请用解析类运行一下这篇文档，看看它与上一篇技巧文章中的那个没有定义命名空间的XML的输出有什么区别。
Run this document through your parser class, and see how it differs from the simpler output of the non-namespaced XML from the last tip.
这就是说，命名空间增加了数据的解析和管理难度。
That said, namespaces make it a lot tougher to parse and manage the data.
要熟悉名称空间的使用，其中一个难点就是了解如何进行范围解析。
One of the hurdles to getting the hang of namespaces is learning how the scope resolution works.
解析器不仅要处理名称空间的声明、验证它们的正确性，而且还要确保XML文档是名称空间格式良好的。
A parser not only processes namespace declarations, verifying their correctness, but it also ensures that an XML document is namespace well-formed.
缓存代理能处理任何可以通过DNS解析的LSID，所以它的已知uri列表在理论上是LSID全局空间的列表。
The caching proxy can process any LSID that is resolvable via DNS, so its list of known URIs is technically the global space of LSIDs.
MQ拓扑对注册中心命名空间的模仿越接近，垂直通过各层时的名称解析就越透明和无冲突。
The closer the MQ topology models the registry namespace, the more transparent and frictionless name resolution becomes as it moves vertically through the layers.
与此类似，解析器必须遍历属性集来定位所有的名称空间声明。
Similarly, the parser must always iterate over the set of attributes to locate any namespace declarations.
指出名称空间能帮助解析和查询数据，并能帮助分隔两家公司的定义。
Indicating the namespace assists in parsing and querying the data, and in keeping the definitions of the two companies separate.
W3C似乎开始转变对名称空间uri的看法，将它看作不需要根据一些引用框架进行解析的字符串。
The W3C appears to be moving toward treating the namespace URI as a string that does not need to be resolved against some frame of reference.
这个解析器假设应用程序能够提前将用户输入分成两部分：关键字查询和空间查询。
This parser assumes that an application can split up the user input ahead of time into two parts: the keyword query and the spatial query.
本文用空间解析几何方法，推导了在一般非平行斜入射光条件下，裂纹体表面所形成的反射焦散线和初始曲线的方程。
The equations of caustic curve and its initial curve for a crack illuminated by an oblique incident light beam in reflection arrangement were deduced using the space analytic geometry method.
当然，仍然有可能不能正确地处理一些其他的xml文档——例如，上面我们试过的名称空间xml文档testns . xml遇到了EXPAT解析器失败。
Of course, it is still possible that some other XML document would not be processed correctly — for example, the namespace XML document testns.xml that we tried above fails with the EXPAT parser.
XMLSchema提供了更好的解决方案：告诉解析器从文档名称空间加载模式。
XML schema offers a better solution: Tell the parser to load the schema from the document namespace.
提供名称空间解析的必要性
QueryPath附带的例子展示了如何设置连接参数、对SPARQL 端点执行 SPARQL 查询以及解析复杂的、多名称空间的文档。
The examples that ship with QueryPath show how to set connection parameters, execute SPARQL queries against SPARQL endpoints, and parse complex, multi-namespaced documents.
当然，大多数时候xml解析器并不了解您将要导入的命名空间，所以有必要指定schemalocation属性，并且很容易忘记该属性其实仅仅是一个提示。
Of course, most of the time you will be importing namespaces that the XML parser knows nothing about, so the schemaLocation attribute becomes necessary, and it's easy to forget that it's only a hint.
应用推荐