Skip to main content
Jump to: navigation, search

Difference between revisions of "Data Range"

(fixed references and wordsmithing)
(Predefined Data Ranges)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Introduction ==
+
{{#eclipseproject:technology.higgins}}
This page describes the concept of a [[Data Range]].
+
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 +
== Version ==
 +
This pages describes the concept of [[Data Range]] used in [[Context Data Model 1.1]].
  
 
== Definition ==
 
== Definition ==
* A [[Data Range]] defines the datatype and [optionally] constraints on the value of an [[Attribute]]
+
* 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]] 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 [http://www.w3.org/TR/xmlschema-2/#rf-facets Constraining Facets] section of XML Schema Part 2. They include:
 
* 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 [http://www.w3.org/TR/xmlschema-2/#rf-facets Constraining Facets] section of XML Schema Part 2. They include:
Line 14: Line 16:
 
* 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 [http://www.w3.org/TR/xmlschema-2/#string string] as defined by XML Schema Part 2, but for use in auto-dialing, it might also have a [http://www.w3.org/TR/xmlschema-2/#rf-pattern pattern] facet that constrains the syntax to be valid phone number in North American (e.g. it is of the form (NNN)-NNN-NNNN).
 
* 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 [http://www.w3.org/TR/xmlschema-2/#string string] as defined by XML Schema Part 2, but for use in auto-dialing, it might also have a [http://www.w3.org/TR/xmlschema-2/#rf-pattern 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 Range]]s ==
 
The following are predefined in HOWL:
 
# [[ContextIdDatatype]]
 
# [[NodeIdDatatype]]
 
  
== See Also ==
 
* [[Attribute]]
 
* [[Higgins Global Graph]]
 
  
== Links ==
+
[[Category:Context Data Model 1.1]]
* [http://eclipse.org/higgins Higgins Home]
+

Latest revision as of 00:04, 10 November 2010

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

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).

Back to the top