head	1.8;
access;
symbols;
locks; strict;
comment	@# @;


1.8
date	2009.11.25.03.14.34;	author GarryJolleyRogers;	state Exp;
branches;
next	1.7;

1.7
date	2009.11.20.02.45.26;	author LeeBelbin;	state Exp;
branches;
next	1.6;

1.6
date	2007.03.06.17.30.00;	author TWikiGuest;	state Exp;
branches;
next	1.5;

1.5
date	2006.05.04.11.26.31;	author GregorHagedorn;	state Exp;
branches;
next	1.4;

1.4
date	2004.06.21.11.29.59;	author GregorHagedorn;	state Exp;
branches;
next	1.3;

1.3
date	2004.06.11.09.17.28;	author GregorHagedorn;	state Exp;
branches;
next	1.2;

1.2
date	2004.05.26.10.58.28;	author GregorHagedorn;	state Exp;
branches;
next	1.1;

1.1
date	2004.04.21.17.18.54;	author GregorHagedorn;	state Exp;
branches;
next	;


desc
@none
@


1.8
log
@none
@
text
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118874" format="1.1" version="1.8"}%
%META:TOPICPARENT{name="ClosedTopicSchemaDiscussionSDD09"}%
---+!! %TOPIC%

Implicitly we assume that class names are scientific names that work for all languages. That is not necessarily true (diseases, non-biological objects, etc.). We may have to add audience specific versions (which could also be common/vernacular names).

Adding a representation layer is not so much a problem, as that is seems undesirable to have<br/>
 en: Rheum rhaponticum L. (Rhubarb) <br/>
 de: Rheum rhaponticum L. (Rhabarber) <br/>
It would be nicer to separate the language independent scientific from the language dependent name.

However, if SDD is used for non-biological purposes, there may or may not be a scientific, language independent name. Also, the assumption in biology that scientific = language independent may not be correct. In medicine you may want to define both the medical term and a common name for a disease, but the precise term may either be latin or may be a language-specific term.

How should Entities/Classes/Class look like?

-- Gregor Hagedorn - 21 Apr 2004

The proposal for SDD 0.91 makes this a Label with a collection of language-specific (not audience-) Representations. This significantly complicates the <nop>ProxyBaseType, but I received no better suggestions...

-- Gregor Hagedorn - 26 May 2004

%META:TOPICMOVED{by="GregorHagedorn" date="1086945447" from="SDD.AudienceSpecificClassNames" to="SDD.LanguageSpecificClassNames"}%
@


1.7
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1258685126" format="1.1" reprev="1.7" version="1.7"}%
d12 1
a12 1
However, if BDI.SDD is used for non-biological purposes, there may or may not be a scientific, language independent name. Also, the assumption in biology that scientific = language independent may not be correct. In medicine you may want to define both the medical term and a common name for a disease, but the precise term may either be latin or may be a language-specific term.
d18 1
a18 1
The proposal for BDI.SDD 0.91 makes this a Label with a collection of language-specific (not audience-) Representations. This significantly complicates the <nop>ProxyBaseType, but I received no better suggestions...
@


1.6
log
@Added topic name via script
@
text
@d1 2
a4 2
%META:TOPICINFO{author="GregorHagedorn" date="1146741991" format="1.0" version="1.5"}%
%META:TOPICPARENT{name="ClosedTopicSchemaDiscussionSDD09"}%
d12 1
a12 1
However, if SDD is used for non-biological purposes, there may or may not be a scientific, language independent name. Also, the assumption in biology that scientific = language independent may not be correct. In medicine you may want to define both the medical term and a common name for a disease, but the precise term may either be latin or may be a language-specific term.
d18 1
a18 1
The proposal for SDD 0.91 makes this a Label with a collection of language-specific (not audience-) Representations. This significantly complicates the <nop>ProxyBaseType, but I received no better suggestions...
@


1.5
log
@none
@
text
@d1 2
@


1.4
log
@none
@
text
@d1 19
a19 18
%META:TOPICINFO{author="GregorHagedorn" date="1087817399" format="1.0" version="1.4"}%
%META:TOPICPARENT{name="SchemaDiscussionSDD09"}%
Implicitly we assume that class names are scientific names that work for all languages. That is not necessarily true (diseases, non-biological objects, etc.). We may have to add audience specific versions (which could also be common/vernacular names).

Adding a representation layer is not so much a problem, as that is seems undesirable to have<br/>
 en: Rheum rhaponticum L. (Rhubarb) <br/>
 de: Rheum rhaponticum L. (Rhabarber) <br/>
It would be nicer to separate the language independent scientific from the language dependent name.

However, if SDD is used for non-biological purposes, there may or may not be a scientific, language independent name. Also, the assumption in biology that scientific = language independent may not be correct. In medicine you may want to define both the medical term and a common name for a disease, but the precise term may either be latin or may be a language-specific term.

How should Entities/Classes/Class look like?

-- Gregor Hagedorn - 21 Apr 2004

The proposal for SDD 0.91 makes this a Label with a collection of language-specific (not audience-) Representations. This significantly complicates the <nop>ProxyBaseType, but I received no better suggestions...

-- Gregor Hagedorn - 26 May 2004
@


1.3
log
@none
@
text
@d1 2
a2 2
%META:TOPICINFO{author="GregorHagedorn" date="1086945447" format="1.0" version="1.3"}%
%META:TOPICPARENT{name="SchemaDiscussion"}%
@


1.2
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1085569108" format="1.0" version="1.2"}%
d19 1
@


1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1082567934" format="1.0" version="1.1"}%
d15 4
@