[
https://issues.apache.org/jira/browse/STANBOL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067682#comment-13067682
]
Olivier Grisel commented on STANBOL-3:
--------------------------------------
For the namespace, we will need to first revise the Stanbol enhancement
structured proposed by Rupert and agree on it (we will probably need several
iteration of drafts + sample usage examples in both turtle and JSON-LD to
better grasp the impact on the client). Once a consensus emerges we will have
to organize a vote on the mailing list and refactor the existing engines to
align them all to the new data model.
However I would rather postpone this discussion to after the current release
effort. Let say in September or October.
In the mean time we can do small ad-hoc extensions to the "fise" enhancement
vocabularies that will give us use case coverage constraint for the "Big
Stanbol Enhancement Structure" refactoring discussion. We just have to be aware
that the current "fise" vocabulary + extensions will be refactored and
deprecated in the medium term.
> Clearly defined Stanbol vocabularies
> ------------------------------------
>
> Key: STANBOL-3
> URL: https://issues.apache.org/jira/browse/STANBOL-3
> Project: Stanbol
> Issue Type: Improvement
> Reporter: Enrico Daga
>
> The Stanbol software uses some RDF vocabularies with an active role in the
> code (the code refer to these vocabularies).
> For instance, FISE uses a vocabolary for Enhancement description, KReS uses a
> vocabulary for managing ontologies and rules.
> Stanbol vocabularies should:
> - be refactored when moving to stanbol using some common namespace
> - be distributed in a well-formed RDF (which means also well-documented)
> - be collected and versioned in a common svn branch (separated from the one
> of the software code)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
