WPC 2BR Z3#|b"m^d`"  7@ ,Title` `    !Bib1 Use attribute 4 as defined in `"  7 ,Subject   !Bib1 Use attribute 21 as defined in `" 3.3 Attribute combinations ,For purposes of this profile, the attribute combinations below are defined. Each combination consists of the single Bib1 Use, Structure, and Relation attribute listed, and no other attributes.`"  7%  44` `     ! $ Combination:  7H& Combination Name !$<<'Use-04Structure@CF  IRelation  7'  !$<<'-04@CF  I  7' Authornormalized !$<<'Author04Name (normalized)F  IEqual  7( AuthornonNormalized$<<'Author04Name (unnormalized)  IEqual  7h) Title44` `    !$<<'Title-04Phrasepp=@CF  IEqualh)0*0*0*Ԍ 7 Subject` `    !$<<'Subject04Phrasepp=@CF  IEqual ,,Note: the distinction by this profile of the Phrase structure attribute for title and subject is not intended to imply that there is any expectation that a target will behave differently for the Phrase structure attribute than for any other structure attribute. `" 3.4 Normalization ,For purposes of this profile, when the structure attribute "name (normalized)" is supplied (in the Authornormalized attribute combination) the following normalization is implied:`" X,44Names of persons are formulated according to Rule 22.4 of AACR2, and names of corporate bodies and conferences are formulated according to Rule 24.1A of AACR2. A normalized name is all or the first part of a complete name formulated according to these rules.`"4 3.5 Semantic action indicator ,This refers to the ASN.1 identifier 'semanticAction' within the choice 'complex' within 'attributeValue' within 'attributeType' within the type AttributeElement in the APDU definitions. SemanticAction is meaningful only for version 3 of Z39.50.`" 3.6 Boolean Query ,For purposes of this profile "boolean query" refers to a Z39.50 type1 query with multiple operands linked by boolean operators.`" 4. General Requirements A system implementing this profile must support:  7 4.144The bib1 attribute set. An origin must support bib1 attributes as prescribed in 5.1.1. A target must support bib1 attributes as prescribed in 5.2.1. `"4  7 4.244Diagnostics.`"4  7 444.2.1 Origin requirement. The origin must always accept the object identifier for the bib1 diagnostic set (regardless of the protocol version in force). In addition, when version 3 is in force the origin must accept the object identifier for the diagnostic format diag1.`"  7 444.2.2 Target requirement. When version 3 is in force the target must be able to return either bib1 or diag1 diagnostics, as prescribed in 6.2.`"  7 4.344Z39.50 protocol version 2. Conformance requirements that pertain to version 2 are specified in section 5. A system may optionally implement version 3; conformance requirements that pertain to version 3 are specified in section 6.`"4  7(# 4.444MARC record syntax. See section 7. `"4  7# 4.544Preferredmessagesize of 4096. See section 8.`"4 5. Conformance requirements pertaining to Version 2 5.1 Origin requirements 5.1.1 Single Operandh)0*0*0*Ԍ,,An origin must be able to formulate a type1 query with a single operand consisting of an attribute combination and term, for each of the following attribute combinations as defined in 3.3:`" 44 Title, 44 Subject, 44 at least one of Authornormalized and AuthornonNormalized.  7x 5.1.244Boolean Query XAn origin is not required to formulate a boolean query. When the origin does send a boolean query, where each operand is constructed as described in 5.1.1, the associated target procedures are specified in 5.2.3.`" 5.2 Target Requirements  7 5.2.144Bib1 Attribute Set`"4 ,,A target must support the bib1 attribute set. This requirement does not imply that the target must support any specific attributes, with the following exception: the target must support the Relation attribute 'equal'.`" 5.2.2 Single Operand ,,When the target receives a type1 query with a single operand consisting of an attribute combination and term where the attribute combination is of those listed in 5.1.1:`"  7P 5.2.2.1 If the target cannot process the query because it does not support the one or both of the Use attribute and Structure attribute, it should fail the search and return a diagnostic from the bib1 diagnostic set, either 114: "unsupported Use attribute", or 118: "unsupported Structure attribute", as appropriate. `" 44` `  Notes: `"4  7 44` `    (1)4 !In the case where the target does not support either attribute, the target may select which of the two diagnostics to return.`"  7  44 ` `    (2)4 !This specific diagnostic requirement is waived when the target considers some other error condition to take precedence (for example, "permanent system error") in which case the target must return an appropriate diagnostic describing that condition. `"  7 5.2.2.2 If the target supports both the supplied Use and Structure attribute (and there are no error conditions that would otherwise cause the target to fail the search), but there are no records located by the search, the target should indicate "no records" (i.e. searchstatus = success; resultcount = 0) rather than fail the search and return a diagnostic.`" 5.2.3 Boolean Query XIf the target receives a boolean query where each operand is constructed as described in 5.1.1:`"  7' 5.2.3.1 If the target cannot process the query because it cannot support boolean queries, or cannot support the specific boolean operators, or cannot process one of the operands, it shouldh)0*0*0* return an appropriate diagnostic; in the case of multiple errors, the target may select which error condition to report.`"  7 ,,5.2.3.2 If the target can process the query but there are no records located, the target should indicate "no records" (i.e. searchstatus = success; resultcount = 0) rather than fail the search and return a diagnostic.`" 6. Conformance requirements pertaining to Version 3 6.1 Origin Requirements ,When version 3 is in force, the origin should be able to formulate queries as specified in 5.1.1, without including a semantic action indicator. The origin may also, optionally, formulate queries with a semantic action indicator. If the value of the indicator is 1 (May not substitute), the associated target procedures are specified in 6.2. If the value is other than 1, the query is outside the scope of this profile.`" 6.2 Target Requirements ,When version 3 is in force, when the target receives a query as specified in 5.1 which either:`" ,a) does not include a semantic action indicator, or`" ,b) includes the semantic action indicator 1 (May not substitute),`" ,then the rules of 5.2 apply, with the exception noted below. Interpretation of other queries is not addressed by this profile.`" ,Exception: If the target cannot process the query because it does not support an attribute or attribute combination, then as an alternative to using a bib1 diagnostic, the target may use the diag1 diagnostic 1005 ("attribute combination not supported") to report this condition. When using diag1 diagnostic 1005 the target may optionally suggest one or more alternative attribute combinations. For example, if the target does not support the Use attribute 'Author' but does support one or more of the Use attributes 'Authorname personal', 'Authorname corporate' or 'Authorname conference' (bib1 use attributes 1004, 1005, or 1006 respectively) it may report this via diag1 diagnostic 1005.`" 7. Record Syntax requirement A system must support at least one specific national or international MARC variant. (This may be any MARC format whose syntax definition is registered with an object identifier. An initial list is provided in Appendix REC of Z39.501994.) 8. Message Size A system must support a value of 4096 for the Init parameter preferredmessagesize. This means:  7( 8.144,` ` If the origin proposes a value of 4096, the target must accept that value (i.e. must respond with the same value). `"` h)0*0*0*Ԍ 7 8.244,` ` If the origin proposes a value less than 4096:`"`  7  44,` `  o, The target may accept the proposed value.`"  7  44,` `  o, The target may alternatively respond with a larger value, but not greater than 4096, and if so, the origin must accept the target response. `"  7  44,` `  o, The target may not respond with a value less than the proposed  7 value.$<<'hh*`"  7x 8.344,` ` If the origin proposes a value greater than 4096:`"`  7@  44,` `  o, The target may accept that value.`"  7  44,` `  o, The target may alternatively propose a lower value, but not less than 4096, and if so, the origin must accept the target response.`"  7`  44,` `  o, The target may not respond with a value greater than the proposed value.`"