Re: [2600] Need help with some words
Thank you everyone for your suggestions. Many of them were good
suggestions, but none (including my own) were both sufficiently
descriptive without further explanation and consistent in terms of part of
speech. I think that the best solution is to use short phrases, and here's
what I'm proposing:
inTransit: for all kinds of User and TSF data that is being sent or
received over shared medium interfaces
atRest: for all kinds of User and TSF data that is contained in the TOE
For User Document Data only, we have some subcategories of atRest data:
inJob: User Documents that are in an active job, whether pending or
processing
onServer: User Documents that have been stored in the TOE during one job
for subsequent retrieval by another job and/or user
isDeleted: User Documents that have been dereferenced during or after
completion of a job
And a final subcategory of inJob:
toOutput: User Documents that are pending output to a hardcopy handler
For the sake of brevity, I propose to use these names individually and not
include the entire hierarchy. In other words, a User Document that is
pending output would be called "D.DOC.toOutput". It would _not_ be called
"D.DOC.atRest.inJob.toOutput".
Also, I think it would help to use mixedCase for the state names (as shown
in the example above) while retaining ALL CAPS for the data names.
I hope this proposal is acceptable. I haven't made up any new types or
states of data, it's all just naming changes.
Regards,
--
Brian Smithson
Project Manager
PMP, SSCP, CISSP, CISA, ISO 27000 PA
Advanced Imaging and Network Technologies
Ricoh Americas Corporation
(408)346-4435
New address:
10460 Bubb Road
Cupertino, CA 95014-4150
> -----Original Message-----
> From: Brian Smithson
> Sent: Friday, July 27, 2007 12:36 PM
> To: STDS-2600@listserv.ieee.org
> Subject: Re: [2600] Need help with some words
>
> I'm currently using "persistent" instead of "stored" for documents.
> Considered by itself, that's a good word to use, but what I'm really
> struggling with is the other document state in which the
> document is only
> present in the TOE during a job (while pending and during processing).
>
> Previously, I was using "stored" for TSF Data (in contrast to
> "transit"),
> but I am looking for a different word to use there, and I
> don't think that
> "persistent" will work because it doesn't really contrast
> with "transit".
>
> Regards,
> --
> Brian Smithson
> Project Manager
> PMP, SSCP, CISSP, CISA, ISO 27000 PA
> Advanced Imaging and Network Technologies
> Ricoh Americas Corporation
> (408)346-4435
>
> New address:
> 10460 Bubb Road
> Cupertino, CA 95014-4150
>
> > -----Original Message-----
> > From: Haapanen, Tom [mailto:tomh@EQUITRAC.COM]
> > Sent: Friday, July 27, 2007 11:27 AM
> > To: STDS-2600@listserv.ieee.org
> > Subject: Re: [2600] Need help with some words
> >
> > How about "persistent" instead of "stored"?
> >
> > Tom
> >
> > -----Original Message-----
> > From: Brian Smithson [mailto:Brian.Smithson@RICOH-USA.COM]
> > Sent: Friday 27 July 2007 13:59
> > To: STDS-2600@listserv.ieee.org
> > Subject: [2600] Need help with some words
> >
> > I've been working on some comments and action items from last
> > meeting and am
> > looking for words that I can use to distinguish certain kinds
> > of assets.
> > I've spent a few hours browsing and searching online thesauri and
> > dictionaries, and I simply haven't come up with anything very
> > satisfying.
> > Perhaps one of you can help?
> >
> >
> > Here is the situation:
> >
> > AI#372: We had D.DOC.TEMP and D.DOC.STORED, but the notions
> > of "temporary"
> > and "stored" have been consistently confusing for many
> > people. "Temporary"
> > refers to the passage of time, but that is not the correct
> > concept, and
> > "stored" is vague but perhaps also implies something like
> > storage on disk
> > versus memory.
> >
> > The concept that I'm really trying to get across is that
> > D.DOC.TEMP is a
> > document that is present in the TOE only until a job has
> > completed, after
> > which it is deleted. So I am looking for something to replace
> > TEMP which
> > means something like "lasting only for the duration of a
> > particular task".
> > I am also looking for a replacement for STORED in
> > D.DOC.STORED which means
> > that the data persists beyond the end of the job. If we get a
> > good word to
> > replace TEMP, then it will be a little easier to get a
> replacement for
> > STORED.
> >
> > For these words, we should also consider the other states in
> > which documents
> > can exist (TRANSIT, DELETED, and OUTPUT) and make sure that
> > the new words
> > fit well with the other states (or come up with new words for
> > all that play
> > well together).
> >
> > The words I am using at this point are "temporary" and
> > "persistent", but
> > temporary implies a temporal dimension and we're looking for
> > something more
> > like a functional dimension. I am really surprised that I
> > haven't been able
> > to find suitable words somewhere in the field of computer science to
> > describe this concept.
> >
> >
> > AI#375: Sharp made the astute observation that the NVS TOE
> > must provide
> > protection against salvage of TEMP and STORED documents, but
> > in doing so, it
> > implies a requirement to provide a function of storing documents.
> > However, we must also distinguish between these two document
> > states because
> > we don't have STORED docs in all TOEs but we do need that
> > kind of asset (and
> > its special access control policies) in the DSR TOE. My
> > solution, which is a
> > little ugly, is to define TEMP and STORED as special cases of
> > another state,
> > and I need to find a good name for that new state.
> >
> > The distinguishing feature of the new state is that the data
> > is present in
> > the TOE, in contrast to data that is in TRANSIT. This new
> > state would be
> > used for document, function, TSF confidential, and TSF
> > protected data. It
> > should not imply any kind of temporal or functional lifetime,
> > and therefore
> > could be used to represent data that is present only during a
> > job and also
> > data that persists after a job has completed.
> >
> > The word I am using at this point is "at-rest" (to contrast
> > it with "in
> > transit"), but I am not very happy with that choice. I
> > thought about staying
> > with STORED, but that seems to imply permanence and/or disk
> > storage. I also
> > thought about using RESIDENT, but that seems to imply
> > permanence and/or
> > pre-existence or intrinsicality.
> >
> >
> > So, here is the current hierarchy of data classes:
> >
> > DOC
> > .TRANSIT
> > .AT-REST
> > .TEMP
> > .PERSIST
> > .DELETED
> > .OUTPUT
> > FUNC
> > .TRANSIT
> > .AT-REST
> > CONF
> > .TRANSIT
> > .AT-REST
> > PROT
> > .TRANSIT
> > .AT-REST
> >
> > And I am looking to replace ".AT-REST", ".TEMP", and
> > ".PERSIST" with better
> > words.
> >
> >
> > By the way, I also considered using very short phrases
> > instead of single
> > words, like "inTransit" "atRest" "duringJob" etc. As long as
> > they're very
> > short, this might work. If phrases are used, then consistency
> > among them
> > becomes even more important. Think of this in terms of
> > completing a sentence
> > like "this data is in the state of [being] ________" or "this
> > data is in
> > a(n) ________ state".
> >
> >
> > Isn't this stuff fun? Help!
> >
> > Regards,
> > --
> > Brian Smithson
> > Project Manager
> > PMP, SSCP, CISSP, CISA, ISO 27000 PA
> > Advanced Imaging and Network Technologies Ricoh Americas Corporation
> > (408)346-4435
> >
> > New address:
> > 10460 Bubb Road
> > Cupertino, CA 95014-4150
> >
>
>