Chapter parity with ISO 690 DIS; publish CC 6900

metanorma.yml

@@ -5,7 +5,6 @@ metanorma:
     files:
     - sources/cc-6900.adoc
     - sources/iso-6900.adoc
-relaton:
   collection:
     name: Information and documentation -- Bibliographic reference model and serialization
     organization: CalConnect/ISO

sources/cc-6900.adoc

@@ -4,7 +4,7 @@
 :language: en
 :doctype: standard
 :edition: 1
-:status: working-draft
+:status: published
 :revdate: 2019-06-05
 :published-date: 2019-06-05
 :script: Latn

sources/iso-6900.adoc

@@ -10,7 +10,7 @@
 :title-intro-fr: Information et documentation
 :title-main-fr: Modèles de référence bibliographique et d'information sur les citations et sérialisation
 :doctype: international-standard
-:docstage: 00
+:docstage: 40
 :docsubstage: 00
 :technical-committee-type: TC
 :technical-committee-number: 46

sources/sections/02-norm-refs.adoc

@@ -20,3 +20,15 @@ edition of the referenced document (including any amendments) applies.
 * [[[ISO15924,ISO 15924]]], _Information and documentation -- Codes for the representation of names of scripts_
 
 * [[[ISO24229,ISO 24229]]]  footnote:[Under preparation. (Stage at the time of publication ISO/DIS 24229)], _Information and documentation -- Codes for the representation of script conversion systems_
+
+* [[[ISO4,ISO 4]]], _Information and documentation -- Rules for the abbreviation of title words and titles of publications_
+
+* [[[ISO216,ISO 216]]], _Writing paper and certain classes of printed matter -- Trimmed sizes -- A and B series, and indication of machine direction_
+
+* [[[ISO639_1,ISO 639-1]]], _Codes for the representation of names of languages -- Part 1: Alpha-2 code_
+
+* [[[ISO832,ISO 832]]], _Information and documentation -- Bibliographic description and references -- Rules for the abbreviation of bibliographic terms_
+
+* [[[ISO3166_1,ISO 3166-1]]], _Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes_
+
+* [[[ISO3166_2,ISO 3166-2]]], _Codes for the representation of names of countries and their subdivisions -- Part 2: Country subdivision code_

sources/sections/05-data-types.adoc

@@ -8,9 +8,9 @@ image::relaton-models/relaton/images/RelBib_DataTypes.png[]
 
 Uri:: Container for URIs, as defined by <<RFC3986>>.
 
-Iso8601Date:: Gregorian date, as specified in <<iso8601>>.
+Iso8601Date:: Gregorian date, as specified in <<ISO8601-1>>.
 
-Iso8601DateTime:: Gregorian date and time, as specified in <<iso8601>>.
+Iso8601DateTime:: Gregorian date and time, as specified in <<ISO8601-1>>.
 
 Iso639Code:: Code for language or language family, as specified in <<ISO639>>.
 The specification is open as to whether the two-letter code or the three-letter
@@ -19,7 +19,7 @@ code for languages is used.
 Iso15924Code:: Code for scripts (writing scripts), as specified in <<ISO15924>>.
 
 DateTime:: Type which allows date and time to be specified as either a Gregorian
-date and time, as specified in <<iso8601>>, as text, or as both.
+date and time, as specified in <<ISO8601-1>>, as text, or as both.
 
 TypedUri:: URI associated with a type. The types of URI are open-ended, but include
 the IANA link relations specified in <<RFC8288>>.

sources/sections/06-bibitem.adoc

@@ -2,6 +2,8 @@
 [[bibitem]]
 == Bibliographic Item Model
 
+[[reference_elements_general]]
+
 This clause provides information models that collectively
 provide the necessary data elements for creation of citations and bibliographic references in accordance with <<ISO690>>.
 

sources/sections/07-data-elements/0701-general.adoc

@@ -1,8 +1,39 @@
 
 [[data-elements-general]]
-== Data elements
+=== General
 
-Common data elements used within this document are provided below.
+[[elements-types]]
+==== Types of data elements
+
+Generally, there are three types of data elements in a reference,
+ordered according to the following preferred manner:
+
+* Attributes of the cited information resource;
++
+====
+Creator, title, medium, date of publication.
+====
+
+* Relations of the cited information resource with other information resources;
++
+====
+Translated from, Catalogued in.
+====
+
+* Attributes of the citation.
++
+====
+Date of citation.
+====
+
+
+==== Common rules
+
+===== General
+
+This clause specifies common rules that apply to all data elements.
+
+Common data types used within this document are provided below.
 
 .TypedUri
 image::relaton-models/relaton/images/RelBib_DataTypes.png[]
@@ -39,3 +70,63 @@ FormattedString:: String which is formatted according to conventions specified
 in a named MIME type (<<RFC2046>>).
 
 LocalizedString:: FormattedString which optionally specifies its language and/or script.
+
+===== Adhere to language of publication
+
+Language of phrases such as "`In:`" or "`Available from:`" should be based on the language and script of the publication rather than the contents of the citation.
+
+[example]
+In an article written in Finnish, it is better to use phrases "`Julkaisussa`" ("`In`" in Finnish) and "`Saatavissa`" ("`Available from`" in Finnish) instead of "`In`" and "`Available from`".
+
+NOTE: The language and script of the publication refers to the language and script of the publication containing the references. It is not the language of the cited information resource.
+
+
+[[transliteration]]
+===== Transliteration and transcription
+
+References made in a publication should adhere to the language and script of the publication. This enables the reader of the publication to understand the references.
+
+All data elements that are not in the language and script of publication should be converted to the (main) language and script used in the publication, and presented as associated information to the cited data element, in accordance with the appropriate international or national standard or other technical specification
+on transliteration or transcription.
+
+The script of a data element, and the script conversion system used, are serialised in the script attributes of localized strings (see <<data-elements-general>>).
+
+[example]
+For a publication written in Latin script, any data element in a non-Roman alphabet in the cited information resource is Romanized, with the Romanized portion appended to the data element as associated information.
+
+[example]
+For a publication not written in Latin script, any data element in a Roman alphabet in the cited information resource is transliterated or transcribed to the script used, with the converted portion appended to the data element as associated information.
+
+NOTE: Recommending specific transliteration, transcription or Romanization systems is outside the scope of this document. There can be multiple choices (for instance, ISO 3602, ISO 3602 Strict, Hepburn, JSL, ALA-LC and Wapuro are Romanization systems for Japanese) and publishers can ask the authors to use any of them.
+
+
+===== Abbreviation
+
+Generally accepted bibliographic terms should be abbreviated in accordance with the rules established in <<ISO832>>.
+
+Additional abbreviation rules are available for
+specific resource types are provided in <<resource_types>>, as well as in
+<<series_abbreviation>> for series titles.
+
+Other abbreviations should be avoided unless specified in this document.
+
+
+===== Punctuation and typography
+
+A consistent system of punctuation and typography should be used throughout a list of references and between data elements.
+Each data element within a reference should be clearly separated from subsequent elements by punctuation or change of typeface.
+
+NOTE: In order to emphasize the importance of consistency, a uniform scheme of punctuation is used in the examples in this document. The scheme is purely illustrative and does not form part of the recommendations.
+
+
+===== Associated information
+
+Associated information of a data element includes:
+
+* optional information defined in <<data_elements>> for each data element,
+* optional information defined in <<resource_types>> specifically for resource types,
+* additional information supplied by the citer.
+
+Associated information is usually represented within square brackets: "[" and "]".
+
+In cases where square brackets may cause confusion, a separate sentence may be added to the reference to express the associated data (such as in <<patent-inventors>>).