WissDB . since Jun 15 . Index . DOCs TOP TOC

S_ Set_Content




part of C_WissDB_DL_API


Each object X in the B_Knowledge_Base that has an attribute named a_Loc may also have a presentation of type FILE or URL.

This value is referred to as the Content addressed by the locator X.a_Loc (or, equivalently, as the value of unit( X ) ).


§      In: Locator

        Is to be a locator for data of type E_Aspect, E_Process, E_Role, or E_KnowledgeItem.

§      In: Content

        Is either NULL or the B_URL to an existing file (of which to store a copy in form of a NodeValue).

§      In: Author

        Is either NULL or a value of type D_EmailAddress .

§      Out: AppErrors

        Is to describe an AppError if the given Locator is currently not in use or if the file identified by the B_URL could not be read.

§      Out: ReturnCode is one of the following values:

–      RC_ok

–      RC_syserror

–      RC_seeAppErrors


Has to:

Ensure that, from now on,

§      Content is the new content of the given Locator L, and

§      NULL is the content of all locators of which L is a true preLocator.

§      X.a_contact = Author and X.a_LastUpdate = today for each E_Result X such that X.a_Loc is preLocator of L.


Reading content created this way is possible via S_Get_Content.



Note: For each element X of B_WissDB_Database.E_Result the attribute X.a_since is set only once – it is the day the record was created (so that we see how old a result seen as a unit actually is).


Because of:

C_WissDB_API needs a way to store content (or an URL seen to be a pointer to content).

One reason for using an URL instead of a file may be that the content in question is to be dynamic content created on request, or being stored, by some other system.


WissDB . Index . DOCs . TOC