Thursday, April 19, 2012

Secured Conditional Text


Adobe FrameMaker, Adobe Robohelp and Microsoft Word are some of the commercial tools
that use Conditional text feature in some form or the other. Conditional Text is one of the advanced feature of desktop publishing tools used mostly for Single Sourcing of a document. This feature is highly used in industry all over the world from writing Specifications to
Documentation of a product. Using this feature, different versions of a document can be maintained.

conditional text: text that may have alternate renderings, based on what the conditional text
is referenceing ... see http://www.livelinx.com/contentmanagement/conditionaltext.
html

As of now, we may show/hide conditional text created by any user in a document. There is no security implemented with the show/hide of the text.
Creating security at user level, based on Conditions tag can be useful for a document, as all users cannot edit/view other users text in the document. There are cases where Administrator of document wants to ensure certain part of document to be hidden from users, meanwhile allowing other users to have permissions of their respective sections.

The intent is to implement permission based conditional text so that the creator of conditional tag may define the view/edit permissions associated with it for other users.

Goal: It provides the document with "secure" conditional text such that a text within the document can
be hidden from other users and shown only if the specific user has permissions over it.

Example:
There is a shared file XYZ Now the owner of XYZ is Superuser. He creates a textA with view permissions to A, and textB with view permissions to B. Now when the file XYZ is opened by B he may not be able to see the text created for A. 

Now A can create an attribute over textC for which he gives permissions to B, then B can also view this text. It can be extended to edit permissions as well. If Superuser gives edit permissions for textA to A,
he may change the textA attributes as well.'

(this was coined along with my colleague: Ankur Prakash)

No comments: