因此，只要关注分离所需的抽象存在，我认为可以不使用任何特定的图书馆。
Therefore, as long as the separation of concern and required abstraction is present, I think it would be OK not to use any specific library.
这真的没有什麽不一样的，唯一的不同只是，音乐是一个无形的抽象存在而非有形实体。
There's really no difference except for the fact that music is something intangible and abstract and not a physical entity.
直接知识的原则应该排斥无规定性的空洞直接性（抽象存在或纯粹的、自为的统一），而力持理念与存在的统一。
The maxim of immediate knowledge rejects an indefinite empty immediacy (and such is abstract being, or pure unity taken by itself), and affirms in its stead the unity of the Idea with being.
这就需要从思维方式上变革“实体化社会观”，因其实质是传统本体论的思维方式，它将社会视为在人之上的抽象存在。
So it needs to change subjective social view from thinking way, it means change traditional thinking method; it sees the society as an abstract existence upper then human.
作者建造的抽象系统仅仅存在于他的脑海里，它的物理表现(书)仅仅是为了方便的保存和发行的一种手段。
The abstract system that an author constructs exists only in his mind, and the physical manifestation — the book — is only a convenient means of storage and distribution.
我们是否能推断：服务是客观实在的，通过给它命名，我们就让像“存在”这样的事物被抽象了出来？
Might we conclude that a service is a reification, that by naming it we have given thing-like existence to an abstraction?
我们常常趋于相信消极与积极是对立面，以一种抽象的方式，彼此分离，是彼此敌对的存在。
We often tend to believe that negative and positive are opposites, separate from another and, in an abstract way, enemies of one another.
从你的角度来看，在不同层次上的抽象显得有些过于的形式主义，因为它很典型模拟了不同层次的之间存在的现象。
From your point of view these are formalisms that occur at different levels of abstraction, since they typically model phenomena at different levels of granularity.
就这门课程中理论的抽象程度而言，没必要把它，用于实践，但是在绝大多数情况下，理论无疑都是为了实践而存在。
At this level of abstraction, plainly there isn't all that much incentive to apply thinking of that kind, but on the other hand undoubtedly theory does exist for the most part to be applied.
如果数学思想在某处等待着被发现，那么即使人类从未构想，一个纯粹抽象的概念也必须存在。
If the mathematical ideas are out there, waiting to be found, then somehow a purely abstract notion has to have existence even when no human being has ever conceived of it.
“一切都是节点”的抽象还因为存在一些节点类型和访问方法一致性的缺乏而丧失了一些价值。
The everything-is-a-node abstraction also loses some value because of the number of node types that exist and because of the lack of uniformity present in their access methods.
世界上并不存在，无法谈论抽象概念的语言。
There's no language in the world that you just cannot talk about abstract things with.
由于存在的节点类型数量及其访问方法缺乏一致性，“一切都是节点”的抽象丧失了一些意义。
The everything-is-a-node abstraction loses some value because of the number of node types that exist, and because of the lack of uniformity present in their access methods.
因而,数字2,数字3,不管它们是什么,至少它们都是不存在于时空中的,柏拉图式的抽象实体
So the number two, the numbers, three, whatever it is, whatever they are, are these Platonic abstract entities that don't exist in space and time.
我们精心考虑的每一项软件抽象几乎都存在与之相反的方面。
It's almost as if every one of our carefully considered software abstractions is being targeted by a dedicated team of contrarian ninjas.
了解了这点，就能注意到top对象类是抽象的，这意味着它的存在只是为了让其他对象类能够扩展它。
Knowing this, you can note that the top object class is abstract, which means it only exists so that other object classes can extend it.
然而，存在着这样的情况，在流程开发时，实现抽象web服务的服务端点是未知的。
However, there are scenarios where the service endpoint that implements an abstract web service is unknown at process development time.
这种映射需要实际的物理数据所在位置与域模型（包含在Initiate的数据字典内）之间存在抽象级别。
This mapping requires an abstraction level between the actual physical data location and the domain model, which is contained in Initiate's Data Dictionary.
模型的许多价值存在于抽象的关注个别的关注点。
Much of the value of models lies in abstracting away details to focus on separated concerns. How much you model depends on what level of abstraction you need to understand.
Rails的核心组件始终存在，即RESTful路径、关系、验证、模板和数据库抽象化。
Rails's core components-restful routes, relationships, validations, templates, and database abstractions-persist.
SOA最大的技术挑战是服务抽象的创建和维护。 商业服务隐藏了存在于背后的IT商业和用户的复杂性，然而复杂性是真真切切存在的，SOA实际上增加了背后的复杂性。
The greatest technical challenge with SOA is creating and maintaining the service abstraction
宽泛地讲，计算机程序员们的工作就是去设计有用的抽象概念，即观察现实世界中存在的东西，并在计算机中创建这些东西的有用的模拟物。
In a broad sense, a computer programmer's job is to design useful abstractions — to see things that exist in the real world and to create useful simulations of them on the computer.
逆向工程是对一个已存在系统的分析处理，以鉴别它的组成部分及它们的内在联系，从而以高层抽象性来构建一个系统的框架。
Reverse engineering is a process of analysing an existing system to identify its components and their interrelationships and to create representations of the system at a high level of abstraction.
即使它们允许存在多个物理分布的服务实例，但是每个实例都只有一个抽象定义(由组织统一管理)和一个公共实现。
Even if they allow multiple physically distributed instances of services, there is one abstract definition for each — managed by the organization as a whole — and a common implementation.
还存在从较低抽象级别到较高抽象级别的反向转换。
Reverse transformations also exist from lower to higher levels of abstraction.
大部分服务的存在是为了提供和消费信息，同时他们会为我们将复杂的结构转化为更接近于我们业务的抽象表达。
Most services exist to produce and consume information, and they provide us with the ability to leverage complex structures within abstractions that are more relevant to our business.
如果几个对象间存在公共行为，而开发者想要抽象这种行为，那么它就可以创建一个接口并使用它。
If there are several objects that all have the behavior, and a developer wishes to abstract on that behavior, they can create an interface and then use that.
最初设计数据库时，并不存在这样的表，因此这些表需要从抽象的模型中得出，表现为某些实际的数据库结构。
When somebody designed that database, they didn't have tables like this, so they moved from a model of abstract things they wanted to represent into some physical database structure.
国家" 只是个抽象概念,但沙皇这个人是真实存在的
The state was an abstraction, but in the person of the czar it was a reality.
国家" 只是个抽象概念,但沙皇这个人是真实存在的
The state was an abstraction, but in the person of the czar it was a reality.
应用推荐