head 1.8;
access ;
symbols;
locks; strict;
comment @@;
1.8
date 2006.08.30.01.46.01; author DonovanSharp; state Exp;
branches;
next 1.7;
1.7
date 2006.07.13.01.16.07; author DonovanSharp; state Exp;
branches;
next 1.6;
1.6
date 2006.07.06.05.51.22; author DonovanSharp; state Exp;
branches;
next 1.5;
1.5
date 2006.07.05.04.37.08; author DonovanSharp; state Exp;
branches;
next 1.4;
1.4
date 2006.07.04.04.30.56; author DonovanSharp; state Exp;
branches;
next 1.3;
1.3
date 2006.06.07.04.04.50; author DonovanSharp; state Exp;
branches;
next 1.2;
1.2
date 2006.06.02.07.30.07; author DonovanSharp; state Exp;
branches;
next 1.1;
1.1
date 2006.06.01.06.05.11; author DonovanSharp; state Exp;
branches;
next ;
desc
@@
1.8
log
@@
text
@%META:TOPICINFO{author="DonovanSharp" date="1156902361" format="1.1" version="1.8"}%
%META:TOPICPARENT{name="SddContents"}%
---++SDD Part 0: Introduction and Primer to the SDD Standard
---+++3.9 SDD audiences
SDD contains the provision for defining taxon names for each entity to be applied to delivering products targetted at particular audiences, enabling users to be provided with names they are familiar with. For example taxonomists may be provided with scientific names while landholders are provided with common names.
A simple SDD code instance defining audiences has the basic structure shown below and in Example 3.9.1.
%ATTACHURL%/audiences.gif
---++++Example 3.9.1 - Multiple taxon names for a single entity based on intended audience
ExpertiseLevel2ExpertiseLevel5ExpertiseLevel3
The <Representation> element provides a label for the description. This may be useful if the instance document includes multiple descriptions for different purposes, or is intended for publication in multiple languages (see the topic [[SddLanguage][Language support in SDD]].
<ExpertiseLevel> is restricted to values from 0-5. These categories allow the communication of expected expertise between different applications using UBIF.
Recommended interpretations:
* 0 = expertise level undefined
* 1 = elementary school (year 1 to 6);
* 2 = middle school (year 7 to 10);
* 3 = high school (year 11 above) and general public (trying to avoid any specialized terminology or jargon);
* 4 = university students or (partly) trained personnel (using terminology, but avoiding or explaining problematic terminology);
* 5 = experts (using the full range of terminology).
-- Main.DonovanSharp - 01 Jun 2006
%META:FILEATTACHMENT{name="audiences.gif" attr="" autoattached="1" comment="" date="1152753004" path="audiences.gif" size="13582" user="Main.DonovanSharp" version="1"}%
%META:FILEATTACHMENT{name="labelattributes.jpg" attr="" autoattached="1" comment="" date="1149653013" path="labelattributes.jpg" size="33073" user="Main.DonovanSharp" version="1"}%
@
1.7
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1152753367" format="1.1" reprev="1.7" version="1.7"}%
d5 1
a5 1
---+++3.6 SDD audiences
d9 1
a9 1
A simple SDD code instance defining audiences has the basic structure shown below and in Example 3.6.1.
d14 1
a14 1
---++++Example 3.6.1 - Multiple taxon names for a single entity based on intended audience
@
1.6
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1152165082" format="1.1" version="1.6"}%
d9 1
a9 1
%ATTACHURL%/audiences.jpg
d11 1
a11 1
<ExpertiseLevel> is restricted to values from 0-5. These categories allow the communication of expected expertise between different applications using UBIF.
a12 7
Recommended interpretations:
* 0 = expertise level undefined
* 1 = elementary school (year 1 to 6);
* 2 = middle school (year 7 to 10);
* 3 = high school (year 11 above) and general public (trying to avoid any specialized terminology or jargon);
* 4 = university students or (partly) trained personnel (using terminology, but avoiding or explaining problematic terminology);
* 5 = experts (using the full range of terminology).
a64 1
Intended audience may also be specified in any element requiring a <Label> tag
d66 1
a66 1
%ATTACHURL%/labelattributes.jpg
d68 10
d80 1
a80 1
%META:FILEATTACHMENT{name="audiences.jpg" attr="" autoattached="1" comment="" date="1151984801" path="audiences.jpg" size="14801" user="Main.DonovanSharp" version="2"}%
@
1.5
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1152074228" format="1.1" version="1.5"}%
d23 5
d66 5
@
1.4
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1151987456" format="1.1" reprev="1.4" version="1.4"}%
d11 1
a11 1
ExpertiseLevel is restricted to values from 0-5. These categories allow the communication of expected expertise between different applications using UBIF.
@
1.3
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1149653090" format="1.1" reprev="1.3" version="1.3"}%
d11 10
d23 2
a24 1
d39 21
d68 1
a68 1
%META:FILEATTACHMENT{name="audiences.jpg" attr="" autoattached="1" comment="" date="1149652405" path="audiences.jpg" size="6106" user="Main.DonovanSharp" version="1"}%
@
1.2
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1149233407" format="1.1" version="1.2"}%
d9 1
d30 1
d32 2
d35 4
@
1.1
log
@@
text
@d1 1
a1 1
%META:TOPICINFO{author="DonovanSharp" date="1149141911" format="1.1" version="1.1"}%
d3 1
d5 1
a5 1
SDD Part 0: Introduction and Primer to the SDD Standard
a6 1
3.6 SDD audiences
d10 1
a10 1
Example 3.6.1 - Multiple taxon names for a single entity based on intended audience
d12 1
a12 1
d27 1
a27 1
@