You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Michal Krajňanský <mi...@gmail.com> on 2016/10/10 09:41:00 UTC
Stanbol documentation issues
Dear Stanbol Users,
I have been experimenting with Stanbol system and came across few
frustrations on the way. As I understand there has been recent discussion
about the next release. In this regards, I would like to share with you the
following experience:
1) In the documentation to Tika engine there is a typo:
https://stanbol.apache.org/docs/trunk/components/enhancer/engines/tikaengine.html
*"To detect the content type of parsed content. This is only performed if
the no content type is parsed of the cogent type is set to
"application/octed-stream". The detected content type is added to the
metadata of the Content Item."*
This did not work, and after some searching I found that it should be
*octet-stream
*.
2) In the documentation of Graph chain in Configuration Manager, there is a
seemingly misleading information to an inexperienced user:
http://localhost:8080/system/console/configMgr
*"Use the name of the rdf file available via the data file provides (e.g.
the "/sling/datafiles/" directory)."*
In the runtime folder "stanbol", there is a directory substructure:
*stanbol/config/org/apache/sling/datafiles/*
Originally I thought that the chain config files belong there, whereas in
fact, the system looks for the config in this directory:
*stanbol/datafiles*
I am curious, what are the possibilities of contributing to the Stanbol
project, with solving the issues like these.
Best Regards,
Michal Krajnansky
Re: Stanbol documentation issues
Posted by "Companjen, B.A." <b....@library.leidenuniv.nl>.
Hi Rafa,
It appears that the documentation (and the rest of the website) is in a different repository than the code, which is not mirrored on GitHub:
https://svn.apache.org/repos/asf/stanbol/site/trunk/
I found the link on https://stanbol.apache.org/development/website.html.
Regards,
Ben
On 10-10-16 12:26, "Rafa Haro" <rh...@apache.org> wrote:
Hi Michal,
Thanks for your interest in Apache Stanbol. Both the code and the
documentation is available at [1] and [2] as a mirror. Some parts of the
documentation, as you can see, is outdated. Any fix is more than welcomed
indeed. The easiest way is probably to clone the github mirror([2]) and
provide pull requests there.
Thanks a lot!
[1] - http://svn.apache.org/repos/asf/stanbol/trunk
[2] - https://github.com/apache/stanbol
On Mon, Oct 10, 2016 at 11:41 AM Michal Krajňanský <
michal.krajnansky@gmail.com> wrote:
> Dear Stanbol Users,
>
> I have been experimenting with Stanbol system and came across few
> frustrations on the way. As I understand there has been recent discussion
> about the next release. In this regards, I would like to share with you the
> following experience:
>
>
> 1) In the documentation to Tika engine there is a typo:
>
> https://stanbol.apache.org/docs/trunk/components/enhancer/engines/tikaengine.html
>
> *"To detect the content type of parsed content. This is only performed if
> the no content type is parsed of the cogent type is set to
> "application/octed-stream". The detected content type is added to the
> metadata of the Content Item."*
>
> This did not work, and after some searching I found that it should be
> *octet-stream
> *.
>
>
> 2) In the documentation of Graph chain in Configuration Manager, there is a
> seemingly misleading information to an inexperienced user:
> http://localhost:8080/system/console/configMgr
> *"Use the name of the rdf file available via the data file provides (e.g.
> the "/sling/datafiles/" directory)."*
>
> In the runtime folder "stanbol", there is a directory substructure:
> *stanbol/config/org/apache/sling/datafiles/*
> Originally I thought that the chain config files belong there, whereas in
> fact, the system looks for the config in this directory:
>
>
>
> *stanbol/datafiles*
> I am curious, what are the possibilities of contributing to the Stanbol
> project, with solving the issues like these.
>
>
> Best Regards,
>
> Michal Krajnansky
>
Re: Stanbol documentation issues
Posted by Rafa Haro <rh...@apache.org>.
Hi Michal,
Thanks for your interest in Apache Stanbol. Both the code and the
documentation is available at [1] and [2] as a mirror. Some parts of the
documentation, as you can see, is outdated. Any fix is more than welcomed
indeed. The easiest way is probably to clone the github mirror([2]) and
provide pull requests there.
Thanks a lot!
[1] - http://svn.apache.org/repos/asf/stanbol/trunk
[2] - https://github.com/apache/stanbol
On Mon, Oct 10, 2016 at 11:41 AM Michal Krajňanský <
michal.krajnansky@gmail.com> wrote:
> Dear Stanbol Users,
>
> I have been experimenting with Stanbol system and came across few
> frustrations on the way. As I understand there has been recent discussion
> about the next release. In this regards, I would like to share with you the
> following experience:
>
>
> 1) In the documentation to Tika engine there is a typo:
>
> https://stanbol.apache.org/docs/trunk/components/enhancer/engines/tikaengine.html
>
> *"To detect the content type of parsed content. This is only performed if
> the no content type is parsed of the cogent type is set to
> "application/octed-stream". The detected content type is added to the
> metadata of the Content Item."*
>
> This did not work, and after some searching I found that it should be
> *octet-stream
> *.
>
>
> 2) In the documentation of Graph chain in Configuration Manager, there is a
> seemingly misleading information to an inexperienced user:
> http://localhost:8080/system/console/configMgr
> *"Use the name of the rdf file available via the data file provides (e.g.
> the "/sling/datafiles/" directory)."*
>
> In the runtime folder "stanbol", there is a directory substructure:
> *stanbol/config/org/apache/sling/datafiles/*
> Originally I thought that the chain config files belong there, whereas in
> fact, the system looks for the config in this directory:
>
>
>
> *stanbol/datafiles*
> I am curious, what are the possibilities of contributing to the Stanbol
> project, with solving the issues like these.
>
>
> Best Regards,
>
> Michal Krajnansky
>