70 lines
1.5 KiB
Plaintext
70 lines
1.5 KiB
Plaintext
head 1.2;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
|
|
comment @# @;
|
|
|
|
|
|
1.2
|
|
date 2005.01.17.14.56.44; author ZhiminWang; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2005.01.07.21.01.54; author BobMorris; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="ZhiminWang" date="1105973804" format="1.0" version="1.2"}%
|
|
%META:TOPICPARENT{name="EditingTools"}%
|
|
---++ This topic is for discussion of possible SDD Editor Design Requirements
|
|
Add and comment -- Main.BobMorris - 07 Jan 2005
|
|
|
|
|
|
---++++ Separation of Terminology and Description editing
|
|
How much Terminology should be editable on the fly?
|
|
|
|
If we really want to limit some authors's right on editing teminology, how about we introduce the Role concept into the editor.
|
|
|
|
---++++ Objects in Descriptions should be offered only where they can actually be used.
|
|
For example, a State not associated with a given Character should not be offered as a choice for coding that character
|
|
|
|
---++++ The Key/key ref mechanism should be hidden from the user, but enforced.
|
|
Users should always get their choices offered by label text not by keyref
|
|
|
|
---++++ <nop>NaturalLanguage and <nop>CodedDescriptions should both be supported
|
|
|
|
---++++ Editor engine interfaces
|
|
The editor engine should be able to be used with many kinds of software, such as editors of other objects (e.g. image content metadata), web services, etc.
|
|
|
|
---++++ Template support
|
|
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1105131714" format="1.0" version="1.1"}%
|
|
a2 1
|
|
|
|
d10 2
|
|
d23 2
|
|
@
|