Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Data Range"

m (logo, category)
(Predefined Data Ranges)
Line 19: Line 19:
 
The following are predefined in HOWL:
 
The following are predefined in HOWL:
 
# [[ContextId Data Range]]
 
# [[ContextId Data Range]]
# [[NodeId Data Range]]
+
# [[EntityId Data Range]]
  
 
== See Also ==
 
== See Also ==

Revision as of 14:26, 22 April 2008

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

Introduction

This page describes the concept of a Data Range.

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:

  1. ContextId Data Range
  2. EntityId Data Range

See Also

Back to the top