Z39.50 Utility Attribute Set

Draft 2

January 29, 1999
For discussion at the March '99 ZIG meeting.

The Utility attribute set defined values (for the attribute types defined for Class 1, as specified by the Z39.50 Attribute Architecture ) that are independent of any particular domain or community, or values that would otherwise need to be defined in several attribute sets.
Note: Semantics are suppled for some attribute values, and semantics will be added for more values as this attribute set definition matures, but It is not intended that additional semantics will be supplied for values for which the name itself conveys complete and unambiguous semantics. An example is "Date/time Record Added to Database".
  1. Access Point

  2. Semantic Qualifier

  3. Language
    The Language attribute indicates the language of the supplied term. It is a character string based on RFC 1766 .

  4. Content Authority

  5. Expansion/Interpretation

  6. Normalized Weight
    The weight assigned to the term, for purposes of assigning scores to records. An integer from 0 to 1000. May be attached to a term in a request query (submitted by the client in a search request) in which case the supplied value indicates the weight that the client requests be attached to the term. May be attached to a term in a response query (returned by the server in a search response) in which case the supplied value indicates the weight that the server attached to the term, or the weight that the server recommends for use in a re-submitted query. When supplied by the server the value may be the same as, or different from, the value in the submitted query. May be supplied by the server even if it was not supplied in the request query.

  7. Hit Count
    May be attached to a term in a returned query in the Search response, and its value is the number of records in which the term occurs. Meaningful only in a returned query, although it may occur in a submitted query but should be ignored by the server. (The server should not infer any semantics based on the occurrence of this attribute, however, nor should the server treat its occurrence as an error, because the client may have simply resubmitted a reformulated query or query otherwise previously returned by the server, where the server included a Hit Count attribute.)

  8. Comparison

  9. Format/structure

  10. Occurrence
    Indicates the desired occurrence of the specified access point. Integer. For example, to indicate second author, the value of the Access Point attribute is 'author', and the value of the Occurrence attribute is 2.

  11. Indirection