You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Valentina Presutti (JIRA)" <ji...@apache.org> on 2011/07/19 13:01:58 UTC
[jira] [Commented] (STANBOL-3) Clearly defined Stanbol vocabularies
[ https://issues.apache.org/jira/browse/STANBOL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067618#comment-13067618 ]
Valentina Presutti commented on STANBOL-3:
------------------------------------------
Rupert, sure we're happy to help if this is still a valid request.
I agree with Olivier, we should not be bound to schema.org although we should support it - even by default if you think it's a good idea.
However, I wanted to go back to the namespace issue :) which is a completely different one.
If Stanbol uses and deploy some vocabulary they should have a stable URI.
We can use the PURL service, or have a stanbol@apache base URI, the important think is that it's associated with a description (see linked data guidelines) and it's stable.
Did you rich any decision? Maybe I missed something, sorry!
> 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