102 lines
3.4 KiB
Plaintext
102 lines
3.4 KiB
Plaintext
head 1.4;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
expand @o@;
|
|
|
|
|
|
1.4
|
|
date 2009.11.25.03.14.42; author GarryJolleyRogers; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2009.11.20.02.35.37; author LeeBelbin; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.05.10.08.56.43; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118882" format="1.1" version="1.4"}%
|
|
%META:TOPICPARENT{name="BDI.SDD_.SchemaDiscussion"}%
|
|
---+!! %TOPIC%
|
|
|
|
Many UBIF features are controlled through [[EnumeratedValues][enumerated values]] (i.e. a controlled vocabulary).
|
|
|
|
Enumerated values are used in two cases:
|
|
1 To create a main/subclass hierarchy. Example: all Representation/Label elements are structurally identical, but we desire to further specify detailed semantics of labels. For this purpose, the Label element has a role attribute, with controlled values like Full, Short, Abbrev, Sort for the default full label, short and abbreviated equivalents, and a label preferred for sorting purposes. Note that although the use of role is related to value-based weak typing, in the context used in UBIF it is used only when the subclass have identical syntax and structure to the superclasses.
|
|
2 To express machine-readable semantics for application interoperability. Example: Applications need to know what the status value for missing data is, or which statistical measure has been used.
|
|
|
|
In version 1.0 and 1.1 of UBIF (and BDI.SDD_) we use fully constrained schema enumerations. It is not possible to add further values. However, this is intended to be a preliminary restriction to ensure that a community consensus about relevant is reached. Ultimately, these values should be extensible through URIs.
|
|
|
|
TEI defines [[http://www.tei-c.org/P4X/ref-VALLIST.html][three kinds of value lists]]:
|
|
* closed = only the values specified are permitted.
|
|
* semi = all the values specified should be supported, but other values are legal and software should have appropriate fallback processing for them.
|
|
* open the values specified are sample values only.
|
|
|
|
In future versions we intend to make most, or perhaps all enumerations of the kind "semi". Applications builders are asked to write their code in consideration of this.
|
|
|
|
-- Main.GregorHagedorn - 10 May 2006@
|
|
|
|
|
|
1.3
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
a2 2
|
|
%META:TOPICINFO{author="LeeBelbin" date="1258684537" format="1.1" reprev="1.3" version="1.3"}%
|
|
%META:TOPICPARENT{name="BDI.SDD.SchemaDiscussion"}%
|
|
d11 1
|
|
a11 1
|
|
In version 1.0 and 1.1 of UBIF (and BDI.SDD) we use fully constrained schema enumerations. It is not possible to add further values. However, this is intended to be a preliminary restriction to ensure that a community consensus about relevant is reached. Ultimately, these values should be extensible through URIs.
|
|
d20 1
|
|
a20 1
|
|
-- Main.GregorHagedorn - 10 May 2006
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@Added topic name via script
|
|
@
|
|
text
|
|
@d1 2
|
|
a4 2
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1147251403" format="1.1" version="1.1"}%
|
|
%META:TOPICPARENT{name="SDD.SchemaDiscussion"}%
|
|
d11 1
|
|
a11 1
|
|
In version 1.0 and 1.1 of UBIF (and SDD) we use fully constrained schema enumerations. It is not possible to add further values. However, this is intended to be a preliminary restriction to ensure that a community consensus about relevant is reached. Ultimately, these values should be extensible through URIs.
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
@
|