watson and custom concepts - ibm-cloud

Correct me if I'm wrong, Watson is only able to recognize concepts(no entities) that exist on DBpedia, right?
If not, I would be thankful if you could tell me what is the correct way to recognize custom concepts i.e. to recognize those that don't exist on DBpedia?

Watson NLU/WKS do not currently support customization of concepts.

Related

Self-hosted framework for translation like google translate api?

I am currently developing an enterprise software. The client stated the need to translate certain texts that we gather from different sources into their home language, or at least into English. Due to GDPR concerns we cannot use external APIs like Google Translate API or DeepL. We need to have either a self-hosted solution or even better, just a python framework that contains translation logic for different languages internally.
Do you know of any such framework?
LibreTranslate seems to be a good option that we will be trying out.

Watson Custom sentiment

I am new to Watson, and have a fairly basic question. I understand that custom models can be created for discovery, but not sure about the sentiment model
In my domain there are certain verbs and adjectives that indicate positives and negatives, and Id like to train the sentiment model to identify these. Is this posible?
Thanks in advance,
JDG
For sentiment models, I'm assuming you're referring to Watson NLU. If so, then yes, you can create custom models via Watson Knowledge Studio and use them in the API. Full documentation can be found here.

Writing my own custom context for JSON-LD

I am attempting to create a JSON-LD context which can be used in a closed / intranet environment with no access to the internet.
To this end I am trying to create my own context as there may be licensing issues copying schema.org wholesale and redistributing it.
I've seen that creating your own context is possible but I can't see anywhere that explains what the definition of that context should be. Can someone explain what it should be or point me at a description of an existing context as a starting point?
The official JSON-LD specification should tell you everything you need. Don't be scared by the word specification, it's written more like a tutorial than a typical spec.

Converting SOAP to REST?

I have a web app, that also has an iPhone and Android app using the same API. It hasn't yet been made publicly available, so I wanted to look to convert from SOAP to REST.
I was only able to find a few tutorials that go into thorough explanations of how to code a REST web service, and of those I only found the MSDN one useful. The problem is I got really confused when they started using URI data types inside the object.
My question is, if you are converting SOAP to REST, do you have to recreate all the objects to add the URI? Am I not able to just have a REST entry point, then call one of the classes that retrieve the data?
Once the REST service is made it will only be used by my mobile apps, but not the website (since that can directly access the classes), which makes me not want to change the objects to add a URI. Is that a correct assumption to make, or should the web services also be called by the website?
Sorry if these are newbie questions, but I am struggling to get my head around REST, and I haven't had much experience creating the architecture of potentially high user base apps.
If anyone is able to point me to an actual code set, that would be helpful.
Edit: I am using VS2010, coding in C# and .Net 4.
Thanks a lot,
Andy
Im doing a very similar thing right now :). Rest via wcf isnt too hard, you do have to sometimes add your endpoints in the web config and give it the [webget]/[webinvoce] attributes in the refrence.cs of the web refrence when consuming though c# which is annoying.
Here is a code set i used when getting started. There are a few more on code project too.

How do forwarding types apply to IoC?

I'm still learning Castle Windsor and I see that it supports forwarded types - a term I was unfamiliar with.
Quick Google search and I found this article that explains it pretty throughly however I still don't understand how this applies to IoC or how I would use them from a container and for what reason.
Can anyone explain?
Type forwarding is a way to move type from one assembly to another without introducing breaking changes it has nothing to do with IoC. So you should not worry about this feature :)
Oh man, just did a google search on 'Castle Windsor "Forwarded Types"' and got redirected right back to SO:
Using Castle Windsor configuration files is it possible to delegate to another item declaration?
and from there:
What are “ForwardedTypes” in the context of Castle Windsor component registration?
Maybe Jeff and the team should just give up on trying to have their own search and use google's.