[
https://issues.apache.org/jira/browse/STANBOL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984158#action_12984158
]
Rupert Westenthaler commented on STANBOL-39:
--------------------------------------------
I would like to add, that in my opinion we should be very careful in defining
top level namespaces.
In my point of view every top level namespace should point to a stanbol
component that can be used on there own without any required dependencies to
other stanbol.** component (with the exception of stanbol.web and
stanbol.commons).
Different aspects/functionalities of such components should use sub-namespaces.
e.g. The built-in enhancement engines will use "stanbol.enhancer.engine.**"
Storage implementations of the entityhub will use "stanbol.entityhub.yard.**"
...
I think that "stanbol.reasoning" would make it very clear for
non-semantic-web-specialists what KreS is all about. In that I completely agree
with the comment by Olivier. I see it like that that all the refactoring,
ontology management, knowledge engineering functionalities envisioned by KreS
are all aspects of the geal to bring bring reasoning capabilities to an CMS.
Therefore a +1 for "stanbol.reasoning" from my side.
Within that top level namespace one could find thinks like
stanbol.reasoning.servicesapi: definition of the java API analog to FISE
(stanbol.enhancer)
stanbol.reasoning.ontologymanageer
stanbol.reasoning.refactor
...
best
Rupert Westenthaler
> Rename the KReS java package
> ----------------------------
>
> Key: STANBOL-39
> URL: https://issues.apache.org/jira/browse/STANBOL-39
> Project: Stanbol
> Issue Type: Improvement
> Components: KReS
> Reporter: Olivier Grisel
>
> New name: org.apache.stanbol.reasoning or org.apache.stanbol.reasoner (I
> don't remember what was decided, I cannot find the email, please comment
> below).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
