Conference vaxuum::online_bookbuilding

    I see your problem. This is a completely new requirement for online
    documents and will require some thinking. A non-scrolling line at
    either the top or the bottom of the window sounds like a good solution
    but would require new Bookreader functionality and that will not
    happen before V2.0. There may be something we can do in TeX, a la
    running heads, but I think the best way to do that (for all forms
    of output) would be to design a new structural tag, i.e., 
    <security_notice> (rather than using <running_head>). I will make
    a note of this requirement. Please feel free to send me any
    comments and suggestions.
    
    Thanks,
    
    Mary

Suggest also checking with legal.  The requirements for such notifications
have probably not been reviewed with respect to online documentation and
they may differ from the approach taken with paper.

Nonetheless, the fixed bar sounds like a good approach, perhaps along with
an icon or hotspot that can bring up full topic should the authors want to
say more (or perhaps use it in some way other than security classification).

Legally, I think of online documentation as software, not text.  I've nearly
got the law department convinced that we should treat it so, and take
advantage of any/all software protection law in addition to traditional
copyright.

Unlike our current paper texts, OLD will require that customers obtain
the "right to read" through a software license for BookReader files
themselves (as opposed to the BookReader itself which is licensed under
the VMS license).

(Hmmm, someone should tell Digital bookstores they cannot sell OLD as
they have conventional texts in the past ... ok, tell Pmgt.)

By the way, OLD overwhelming meets the legal definition of "software", or
so our lawyer opined (unofficially).  The BookReader files comprise
"instructions to the computer for the display of data" and are not, in
and of themselves, "documentation".

- greg

    During development of most new products most of the information is
    classified "DIGITAL RESTRICTED DISTRIBUTION".

    Need clarification of how we can produce and distribute online books 
    (at least internally) classified "DIGITAL RESTRICTED DISTRIBUTION".  
    Information classified "DIGITAL RESTRICTED DISTRIBUTION" can not be 
    distributed electronically.

    RE: 39.3. I have forwarded your request to OLD product management
    (Marian Weisenfeld, STAR::) with a request for guidance/info.
    
    Mary

    Well, I don't have a complete answer for this one, but have raised the
    question to the legal department.  It appears on the surface of things
    that one might need some sort of protection (such as an LMF license) to
    restrict access to particular documents.  How this could be implemented
    is another story!
    
    I also asked about using CDROM or other media for restricted
    distribution.  Documentation media could be sent through interoffice
    mail, installed on the reviewer's system with ACLs, and then the
    reviewer alone could access the online documentation file.  This, too,
    is somewhat of a convoluted idea...but that's why I went to the legal
    department.
    
    When they provide me with some information, I'll be posting it here.
    
    Regards,
    Marian
    
    BTW...other ideas are certainly welcome!

    When we produce documents they are almost always labeled in some
    way, e.g. Digital Internal Use Only, Draft, etc. The <dec_security> 
    tag has provided an answer to most of our requirements, and the
    "DRAFT" DVC$PROLOG.PS has done the rest. But, like Al in .0, we
    lose this functionality when the document is put online. 

    The <dec_security>(INTERNAL) tag caused the strange behavior of
    every paragraph was labeled "Digital Internal Use Only" and there
    was about 3 inches of slider bar of whitespace between paragraphs.
    (At first I thought there was nothing but whitespace, but there
    is something.) fortunately I found 
    <ifdef>(_decw_topic\|<define>(dec_security\)&\)
    to avoid the problem and the book becomes readable.

    Is there any way to get the tag to work as expected?
    Is there any way to produce an overlay similar to the one done for
    postscript output?

    thanks,
           mike

    Did anyone ever answer Mike Taylor in .6?  More and more groups are
    using Bookreader for internal documents, and the security labels must
    be placed in the books.  We are encountering this problem now. 
    Labeling them once is not enough, because you can open to anywhere
    within the document.
    
    Please let me know if anything can be done.  This will continue to come
    up.  In .1 (I think it was .1), Mary Utt said that it wouldn't be
    possible until V2, but V2 doesn't have this.  Should we be making sure
    this is included in DECWET::BOOKREADER-REQUIREMENTS?
    
    
    Susan

    Funny you should ask: I got a similar query via MAIL this morning
    and noticed that Mike's note had no reply, although elsewhere there
    are allusions to the fact that the <DEC_SECURITY> tag works online,
    as has been the case since DOCUMENT 1.2B was released. Apologies for
    the non-response.
    
    Anyway, the <DEC_SECURITY> tag can be used for online documents.
    See the 1.2B documentation. The notice is placed at the *top* of
    each topic. Because of the way we 'paginate' for the Bookreader
    (by topic rather than by fixed-length page), we cannot put it at
    the bottom of the 'page', or topic. 
    
    There is a disadvantage to this implementation in that if the topic
    is longer than the text window, the security notice will scroll off
    the window as you scroll through the topic. I have not received any
    feedback that this is unacceptable for security labeling.
    
    We have discussed enhancing the Bookreader such that a small,
    stationery window is overlaid on the text window to carry such things
    as a security notice (see .1). The notice would thus be always visible
    as the text was scrolled. The window would not occlude text: it would
    look like a running head. However, the list of Bookreader enhancements
    is very long and the list of Bookreader developers is very short, so
    this feature has not, to date, had a high priority. My reply in .1 is
    almost two years old. As this point, lack of Bookreader resources has
    pushed this feature out beyond V3.0 of the Bookreader.  Clamoring in
    DECWET::BOOKREADER-REQUIREMENTS might raise its priority. 
    
    Meanwhile, there is the <DEC_SECURITY> tag. Please post comments,
    complaints, suggestions for this tag in this notes conference.
    
    Mary
    

My group is about to ship an internal product that will be used widely
throughout the company.  We'd like to ship the documentation on Bookreader.  
The product is a security product, so it seems especially important that we 
adhere to the corporate policy for labelling information.  Below, is an 
excerpt from Corporate Security Standard 10.0, which is the one with which 
we are trying to comply.  Note the paragraph I've marked with asterisks.  

We are going to <set_online_topic>(headn) to a few different settings and
run the samples by the folks who maintain the standard to see if I can get 
a ruling on whether or not current Bookreader functions are adequate.
I suspect they are adequate given the currently available functions (except
for the phrase "and at the end").  I also suspect it would be a good idea
to raise the priority of providing functions more in line with the corporate 
standard for labelling hardcopy material (for example, by providing fixed top 
and bottom windows that change according to the classification of the book or 
topic.  The National Security Administration's guidelines for "top and bottom" 
labelling are nearly identical to the corporate criteria -- another
good reason for raising the priority of providing compatible functions.
The criteria of both organizations could be met at the same time.

I'll post the results of our inquiry.

Scott


Excerpt from Corporate Security Standard 10.0:
--------------------------------------------- 

"Paper Documents:  All Digital classified documents must be
marked with the assigned Digital classification at the top and
bottom of the first page, and at the bottom of all other pages.
The Digital classification stamp should be used.  This requirement
includes transparencies, 35mm slides, drawings, and pictures.
  
Electronic forms:  Files and/or documents in electronic form
must be clearly marked with the assigned Digital classification,
if practical in the same manner as paper documents, using the
graphic Digital classification logo.  If graphics are not
available on the system being used, the Digital classification
should be typed in, and should be made visually evident by
separation from the body of the document, and by using asterisks
to highlight the Digital classification as follows:
When / if printed out from a computer system, these markings
suffice and additional logo stamps are not required.

(Should the marking of electronic form messages, reports, etc.,   *
at the top and bottom of each page be impractical, the            *
classification marking should appear at important places          *
throughout the file or document, such as at major paragraph       *
headers, and at the end.)"                                        *

    Thank you for that information. The results of your inquiry will be
    very useful.
    
    Specific requirements for Bookreader functionality should be entered
    in the DECWET::BOOKREADER-REQUIREMENTS notes conference.
    
    Mary