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

Attribute

Revision as of 21:22, 27 April 2008 by Paul.socialphysics.org (Talk | contribs) (Version)

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

Version

This pages describes the concept of Attribute used in Context Data Model 1.1

Definition

  • Defines a property of an Entity or a Context.
  • Has a type (URI)
  • Has one or more values all of which MUST be unique
  • Has either simple or complex value(s)
  • Simple values:
    • Are literal values (e.g. "green") based on a "base" XML Schema type URI (e.g. string)
    • The allowed value(s) are defined by a Data Range (URI)
  • Complex values are Entities

Kinds of Attributes Defined in HOWL

Examples

The person Bob Smith might be represented as an Entity in the Context of his employer, the Port Control Authority. This Entity might have the following types of Attributes (and associated values) in this Context:

  • email-address = bob@portcontrol.gov
  • phone number = {617-555-1234, 617-333-4321} <-- multi-valued attribute example
  • passport information = ...etc.
  • fingerprint data = ...etc.
  • surname = "Smith"

The surname Attribute in the example above might have a type of http://openschemas.org/2006/person/surname. The schema associated with the containing Context provides metadata about this URI.

This same Bob Smith might also be represented as an Entity in a "customer-to-Clothes-R-Us" Context (this customer's relationship with the Clothes-R-Us merchant. In this Context Bob has these Attributes:

  • platinumCustomer = True
  • preferredColor = "blue"

Open Issues

  1. At present an Attribute cannot have N>1 values if the values are the same. For example a very odd father might name each of his three kids "frank". Thus the father Entity cannot have an attribute "names-of-children" whose values are "frank, frank, frank".
  2. We need to be able to describe the reality that "real world" context providers must restrict attributes to be "closed"

Back to the top