Entry Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 573954,
    "url": "https://info.mzalendo.com/api/v0.1/hansard/entries/573954/?format=api",
    "text_counter": 83,
    "type": "speech",
    "speaker_name": "Hon. Mbui",
    "speaker_title": "",
    "speaker": {
        "id": 1750,
        "legal_name": "Robert Mbui",
        "slug": "robert-mbui"
    },
    "content": "Sometimes bad publicity is good publicity. We have then to protect the names that people can use in their companies. People can use offensive names that may be attractive to the wrong people and make business out of it. I do not support the use of that name though I have given it as an example. The other ones are protected names. There are those names that are connected with State organs, county governments and public authorities. If these names are allowed to be used in the registration of private companies for personal use, chances are that the unsuspecting public might trade with them believing that they are connected and in the process lose money. I want to give an example of the East African Portland Cement (EAPC). If an individual registered a company and purported from the name that it is an affiliate, a connection or a department of the EAPC, what is likely to happen is that, that individual can give orders to people to supply him or her with material believing it is a recognised firm like the EAPC. Probably the material will be given on credit for 60 days but it turns out that that was a conman. It is important to ensure that we do not allow names that are closely related to the names of existing organisations."
}