wiki-archive/twiki/data/TAPIR/EntityMapping.txt,v

97 lines
1.6 KiB
Plaintext

head 1.4;
access;
symbols;
locks; strict;
comment @# @;
1.4
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.3;
1.3
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.2;
1.2
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next 1.1;
1.1
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
branches;
next ;
desc
@Initial revision
@
1.4
log
@Revision 4
@
text
@By mapping entities one can map abstract "classes" and not only properties of classes.
For specimens for example instead of only mapping the catalog number and a taxon name, one wold also map the entity/idea of an specimen:
Simple mapping:
<verbatim>
<Specimen>
<CatalogNumber> - abcd:/DataSets/.../Unit/UnitId
<Name> - abcd:/DataSets/.../Unit/Identifications/.../FullScientificNameString
</verbatim>
Entity mapping:
<verbatim>
<Specimen> - abcd:/DataSets/.../Unit
<CatalogNumber> - abcd:/DataSets/.../Unit/UnitId
<Name> - abcd:/DataSets/.../Unit/Identifications/.../FullScientificNameString
</verbatim>
This would help the wrapper software to decide which RepNode corresponds to which conceptual schema entity.
Thus it would probably solve the EmptyRepeatableRegionProblem
@
1.3
log
@Revision 3
@
text
@d19 1
a19 1
Thus it would probably solve the EmptyRepNodeProblem
@
1.2
log
@Revision 2
@
text
@d17 3
@
1.1
log
@Initial revision
@
text
@d6 3
a8 3
<Specimen> -
<CatalogNumber> -
<Name> -
d13 3
a15 3
<Specimen> -
<CatalogNumber> -
<Name> -
@