Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Data Range"
(→See Also) |
(→Introduction) |
||
Line 1: | Line 1: | ||
{{#eclipseproject:technology.higgins}} | {{#eclipseproject:technology.higgins}} | ||
[[Image:Higgins_logo_76Wx100H.jpg|right]] | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
− | == | + | == Version == |
− | This | + | This pages describes the concept of [[Data Range]] used in [[Context Data Model 1.1]]. |
== Definition == | == Definition == |
Revision as of 21:26, 27 April 2008
{{#eclipseproject:technology.higgins}}
Version
This pages describes the concept of Data Range used in Context Data Model 1.1.
Definition
- A Data Range defines the range of values of an Attribute
- A Data Range MUST have a base XML Schema type (e.g. String)
- A Data Range MAY include a set of constraining "facets" on its value(s). The names and semantics of these facets are taken from the Constraining Facets section of XML Schema Part 2. They include:
- Enumeration (e.g., must be one of {"red", "green", "blue"})
- Pattern (e.g. regular expression)
- Bounding (e.g. less than 5, more than 100)
See the Constraining Facets section of XML Schema Part 2 for detailed specifications and examples.
Examples
- An Attribute might have a value whose Data Range was defined in the schema of its Context as "telephone number". This telephone number Data Range might have a base type of string as defined by XML Schema Part 2, but for use in auto-dialing, it might also have a pattern facet that constrains the syntax to be valid phone number in North American (e.g. it is of the form (NNN)-NNN-NNNN).
Predefined Data Ranges
The following are predefined in HOWL: