OWL 中可以存在命名限制吗?
我们可以将限制定义为命名类吗?我的意思是,不要使用这个:
:myclass owl:equivalentClass
[ rdf:type owl:Restriction ;
owl:onProperty :hasAge ;
owl:cardinality "2"^^xsd:nonNegativeInteger ] .
使用这个:
:myclass rdf:type owl:Restriction ;
owl:onProperty :hasAge ;
owl:cardinality "2"^^xsd:nonNegativeInteger.
可以吗?
Can we define a restriction as a named class? I mean, instead of using this:
:myclass owl:equivalentClass
[ rdf:type owl:Restriction ;
owl:onProperty :hasAge ;
owl:cardinality "2"^^xsd:nonNegativeInteger ] .
to use this:
:myclass rdf:type owl:Restriction ;
owl:onProperty :hasAge ;
owl:cardinality "2"^^xsd:nonNegativeInteger.
Is that ok?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
是的,那绝对没问题。这也许有点不寻常,但据我所知,OWL 规范中没有任何内容强制限制是匿名的。事实上,按照您的建议命名它们可以使在多个类中重用限制变得更加容易。
Yes, that's absolutely fine. It's a bit unusual perhaps, but AFAIK there is nothing in the OWL specs that forces restrictions to be anonymous. In fact, naming them like you suggest makes reuse of restrictions in multiple classes a lot easier.
是的,您可以为限制命名,只需声明一个命名类相当于该限制即可。 OWL 文档中有很多示例,请参见
其中你会发现这样的例子
Yes, you can give names to restrictions, just declare that a named class is equivalent to the restriction. There are plenty of examples in the OWL documentation, see e.g.
where you find examples like