Ecore 派生的 XMI 实例中的引用使用什么查询/路径语言？
假设我有一个 Ecore 模型，其中包含一个包和一些相互引用的类。如果我创建一个“动态实例”，Eclipse 会生成一个 XMI 文件，我可以实例化一些类。包含关系直接序列化为 XMI 中的 XML 树（示例中的 children 元素）。但是，如果我实例化对已包含在树中某处的元素的引用，则编辑器会为 currentChild 属性编写如下所示的路径表达式：
<parent currentChild="//@parent/@children.1">
<children/>
<children/>
</parent>
据我所知，这不是 XPath，因为：
- “
childrens”是元素而不是属性，不必通过“@”引用 - XPath 使用例如
elem[1]和不是elem.1来获取例如列表的第二个 elem
它是什么以及在哪里可以找到有关它的信息？我已经尝试浏览 EMF 页面/规格，但找不到。
Assume that I have an Ecore-model containing a package and some classes that make reference to each other. If i create a "Dynamic Instance", Eclipse produces an XMI-file and I can instantiate some classes. Containment-relations are directly serialized to an XML-tree in the XMI (the children elements in the example). But if I instantiate references to elements that are already contained somewhere in the tree, the Editor writes Path-Expressions like in the following, for the currentChild attribute:
<parent currentChild="//@parent/@children.1">
<children/>
<children/>
</parent>
As far as I know this is not XPath, because:
- The "
childrens" are elements not attributes and have not to be referenced via "@" - XPath uses the e.g.,
elem[1]and notelem.1to get e.g., the second elem of a list
What is it and where can I find a information on it? I already tried to browse the EMF pages/specs but could not find it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个 EMF 片段路径。 Javadoc 是这样描述的：
String org.eclipse.emf.ecore.InternalEObject.eURIFragmentSegment(EStructuralFeature eFeature, EObject eObject)
返回片段片段，当传递给 eObjectForURIFragmentSegment 时，该片段片段将解析为该对象的给定功能中的给定对象。
特征参数可能为空，在这种情况下，如果可能的话，将推断出该特征。默认结果的形式为：
“@feature-name[.index]”
该索引仅用于多值特征；它代表列表中的位置。
参数：
eFeature 将给定对象与该对象相关的特征，或者为 null。
eObject 待识别的对象。
返回：
在该对象的给定特征中解析为给定对象的片段段。
It's an EMF Fragment Path. The Javadoc describes it like this:
String org.eclipse.emf.ecore.InternalEObject.eURIFragmentSegment(EStructuralFeature eFeature, EObject eObject)
Returns the fragment segment that, when passed to eObjectForURIFragmentSegment, will resolve to the given object in this object's given feature.
The feature argument may be null in which case it will be deduced, if possible. The default result will be of the form:
"@feature-name[.index]"
The index is used only for many-valued features; it represents the position within the list.
Parameters:
eFeature the feature relating the given object to this object, or null.
eObject the object to be identified.
Returns:
the fragment segment that resolves to the given object in this object's given feature.