I see this document differently.
但我觉得这份文件有所不同。
I see this document differently. I see it as a vision for America - as a blueprint for our future.
我对这一文件的看法则不然，我把它看作是美国的愿景，是我们未来的蓝图。
So often, we have come to view these documents as simply Numbers on a page or laundry lists of programs. I see this document differently.
我们常常把这些文件视为纸页上简单的几个数据或一串计划清单，我就不这么看。
IA is looking for a full time web developer for Internet Ministry. For detailed job description, please see this document. Please click here for the application form.
联总拟招募一位全职专员，来协助执行每日网路宣牧事宜。详情请看此文件。 联总职员申请表。
This is done at the end of the document processing stream (see Figure 1).
这是在文档处理流程结束时进行的(参见图1)。
When you open a document with this tool, you will see the image of your redacted document in the window.
当用此工具打开一篇文档时，您会在窗口中看到已修订文档的图片。
The same software can see what kind of document it is and in this case of report it's a form.
还是同一个软件，你可以看到这是什么,类型的文件，这个就是申请单。
Interestingly, if not surprisingly, you will see in the XML versions of this document that the representation on the identical document is not unique.
有意思的是——如果不能算吃惊的话，您会从该文档的XML版本中发现同一文档的表示不是唯一的。
This class has the fundamental job of applying an XSLT stylesheet to an XML document (see Listing 2).
该类实现对一个XML文档应用xslt样式表的基本功能(参见清单2)。
As you can see, the transform is creating a software description document in the form we introduced in the first part of this series.
您会看到，转换将以本系列第一部分所介绍的形式创建软件描述文档。
This may seem odd at first, but it turns out to be very powerful — you can see exactly what the document being parsed looks like, including any indenting!
您一开始可能觉得这很奇怪，但是最终会发现这种机制是十分强大的，因为不管某篇待处理的文档中包含多少缩进，您都可以确切地看出文档解析之后将会是什么样子。
This combination both lets you see without ambiguity what the markup structure of a document is, and also allows you to see a good approximation of a final rendering of an XML document.
这种组合让您清晰地看到文档标记结构，同时让您看到非常近似于最终产生的XML文档。
As we will see, the technique provided in this document can be considered a "last-straw" approach if other approaches have been ruled out.
本文档中提供的技术应该作为其他方法都无效的情况下的最后一招。
In this configuration, the document flows through the pipe (see the sidebar Logging SAX events).
在这个配置中，文档流过管道(请参阅侧栏记录SAX事件)。
The XML document samples provided in the samples folder (see Download) are all valid according to this schema.
Samples文件夹中提供的XML文档示例(见下载)对于这个模式都是有效的。
You should see a pop-up menu with a list of elements that are valid at this point in the document, in this case the HTML element.
您应该看见一个弹出菜单，该菜单列出了文档中这个位置上有效的元素，在这种情况下是html元素。
You see this in Update 22, which succeeds but has no effect on the document.
更新22会成功，但是对文档没有影响。
If you emitted the keys at this point, you'd also see a pair of [studio doc-id] s for each document in the database.
如果您在这个点发出键，您还将看到针对数据库中的每个文档的一对[studiodoc - id]。
To represent this type of document you create the ButterflyFile class (see Listing 4).
为了表示这种类型的文档，要创建butterflyfile类(参见清单4)。
Once this Virtual Field Activity document is filled, we will be able to see the activity in DECS Administrator database (Figure 22)
一旦填写了这个VirtualFieldActivity文档，就可以看到 DECS Administrator数据库中的活动（图 22）。
In this case, you use Schematron to determine the presence of certain elements in an XML document, without modifying the original XML schema (see Listing 3).
在本例中，使用Schematron来决定特定元素在XML文档中的存在，无需修改原始的XML模式(参见清单3)。
See Part 1 of this series for more information about implicit document nodes, the successor to RTFs, when you want tree-structured variables.
如果需要树状结构的变量，有关RTF的后继者及隐含文档节点[implicit document node]的更多信息，请参阅本系列的第1部分。
This count is listed in the Administrative Section of the parent crash document (see figure 10) and is also displayed in all the views in the mail-in database.
这个计数列在父崩溃文档的AdministrativeSection中(见图10)，还显示在mail - in数据库中的所有视图中。
If you save a document with this form and look at the field properties, you see that the field Flags list SUMMARY READ-ACCESS NAMES (see figure 1).
如果使用该表单保存一个文档，然后查看该字段属性，那么将看到FieldFlags列出了SUMMARY READ - ACCESSNAMES(参见图1)。
Because we are using the document literal non-wrapped binding style instead of the document literal wrapped binding style typically used in Integration Developer, we see this unexpected code.
由于我们使用的是文档文字非封装式绑定风格而非IntegrationDeveloper中常用的文档文字封装式绑定风格，我们看到的不是预期的代码。
This tagging may be as simple as document title or as sophisticated as the Library of Congress metacategory method (see Resources).
此标记可以像文档标题一样简单，也可以像美国国会图书馆的元分类 (metacategory)方法（请参见 参考资料）一样复杂。
Not much to it, and you can certainly publish this static document. Readers of it can see something like.
没有什么特别之处，这个静态文档完全可以发布。
One of the technologies that underpins this rapid form of publishing is Rich Site Summary, or RSS (see Resources), an XML document that contains metadata about content items on a site.
支持这种快速发布形式的技术之一是RichSiteSummary或RSS（参阅参考资料），它是一种包含有关站点上内容项的元数据的XML文档。
Select the appropriate document type (use case specification in this case), and click OK (see Figure 8. Branching - Import document 3).
选择合适的文件类型(在本例中，是用例规约)并点击OK(参见图8，“分支—导入文件3”)。
You will see some examples of perform document operations and results later in this article.
在本文后面部分，您将看到一些执行文档操作和结果的示例。
应用推荐