WAIS PROFILE OF Z39.50 V2

FACILITIES

ATTRIBUTE COMBINATIONS

• Use:
  • Any
  • Local number
  • Doc-Id
• Relation:
  • Equal
  • Relevance
• Structure:
  • Free form text
  • Document text
  • Local number
  • URx

• Free-Form (human-entered) Text.
• Relevance Feedback by Document Text.
• Relevance Feedback by Document Identifier (URx).
• Relevance Feedback by Record Identifier (local identifier).
• Search by Document Identifier (URx).
• Search by Record Identifier (local identifier).

• Free-Form (human-entered) Text.
  • Use: Any
  • Relation: Relevance
  • Structure: Free form text
• Relevance Feedback by Document Text.
  • Use: Any
  • Relation: Relevance
  • Structure: Document Text
• Relevance Feedback by Document Identifier (URx).
  • Use: Any
  • Relation: Relevance
  • Structure: URx
• Relevance Feedback by Record Identifier (local identifier).
  • Use: Any
  • Relation: Relevance
  • Structure: Local number
• Search by Document Identifier (URx).
  • Use: DocId
  • Relation: Equal
  • Structure: URx
• Search by Record Identifier (local identifier).
  • Use: Local number
  • Relation: Equal
  • Structure: Local number

RECORD SYNTAX

SCHEMA DEFINITION

1. Tag Types

• Tag Type = 1, for elements from tagSet-1 whose OID is 1.2.840.10003.14.1
• Tag Type = 2, for elements from tagSet-2 whose OID is 1.2.840.10003.14.2
• Tag Type = 3, for occurrences of ObjectElements (locally-defined tags)

2. WAIS Abstract Record Structure

• Headline, Tag path = (2,1), Mandatory and Not Repeatable
• Name, Tag path = (2,2), Optional and Repeatable
• Date, Tag path = (2,3), Optional and Not Repeatable
• Rank, Tag path = (1,10), Optional and Not Repeatable
• Score, Tag path = (1,18), Optional and Not Repeatable
• RecordIdentifier, Tag path = (1,14), Mandatory and Not Repeatable
• URx, Tag path = (1,12), Mandatory and Repeatable
• ObjectElement, Tag path = (3,locally-defined tag), Mandatory and Repeatable

  Headline:

  Set of words that conveys the main idea of the record.

  Name:

  One or more individuals associated with one of the object elements; it could, for example, be an author or an organization. As another example, there might be three object elements: a fingerprint file, photo, and resume; the Name would be the individual that these object elements describe.

  Date:

  A date associated with the record.

  Score:

  Represents the numerical score of the record based on its relevance to the query, from 1 to 1000, inclusive.

  RecordIdentifier:

  An identifier of that record, defined by, and unique within the target system (it may, but need not be, a URx).

  URx:

  Universal Resource Locator or Universal Resource Name for the record.

  ObjectElement:

  Each "object element" contains object information for the record. It may be text, image, etc. Each may be available in one or more variants. As in the above example, suppose there are three object elements: a fingerprint file, a photo, and a resume; the string tags for these three elements respectively might be "fingerPrint", "photo", and "resume". It is recommended that the string tags for the Object Elements be descriptive of the information in the element, for discovery purposes (see description of element set "VARAINT" below). If there are multiple occurences, each must have a different string tag.

  ELEMENT SET SPECIFICATION

  The following element set names should be supported. The latter three are supported with GRS.
  • The primitive element set name "F" is required for conformance. The target will return all elements of the record as specified by the schema, where for each Object Element the applied variant is determined by the target. Large records may not be retrievable using this element set name.
  • The primitive element set name "B" is used to obtain all elements except Object Elements.
  • The primitive element set name "VARIANT" is used to obtain elements with numeric tags, the string tag skeleton, and variant information for each Object Element: the string tag will be indicated for each Object Element, and for each, each variant for that element will be listed, as well as a variant identifier for each variant.
  • The primitive element set name variant identifier (as returned by the target, as a result of a request which use the element set "VARIANT") may be used, to mean: return the first portion of the variant of the element associated with this variant identifier; first portion means from the beginning, as much as fit within the PDU.
  • The primitive element set name target position (as returned by the target in a Generic record) may be used, to mean: return the next portion of the element and variant associated with this target position; next portion means beginning immediately after the end of the previous portion, as much as will fit within the PDU.