relaton / relaton-iec

IecBib: retrieve IEC/CIE Standards for bibliographic use using the BibliographicItem model
MIT License
1 stars 0 forks source link

Validity of IEV `instanceOf` bibitem being a dated document, not an undated reference #58

Closed ronaldtse closed 11 months ago

ronaldtse commented 11 months ago
$ bundle exec relaton fetch "IEC 60050-351"
[relaton-iec] (IEC 60050-351) Fetching from Relaton repsitory ...
[relaton-iec] Downloaded index from https://raw.githubusercontent.com/relaton/relaton-data-iec/main/index1.zip
[relaton-iec] (IEC 60050-351) Found: `IEC 60050-351:2013`
<bibdata type="standard" schema-version="v1.2.5">
  <fetched>2023-11-30</fetched>
  <title type="main" format="text/plain" language="en" script="Latn">International Electrotechnical Vocabulary (IEV) - Part 351: Control technology</title>
  <title type="main" format="text/plain" language="fr" script="Latn">Vocabulaire Electrotechnique International (IEV) - Partie 351: Technologie de commande et de régulation</title>
  <uri type="src">https://webstore.iec.ch/publication/194</uri>
  <uri type="obp">https://webstore.iec.ch/preview/info_iec60050-351{ed4.0}b.pdf</uri>
  <docidentifier type="IEC" primary="true">IEC 60050-351</docidentifier>
  <docidentifier type="URN">urn:iec:std:iec:60050-351::::</docidentifier>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>International Electrotechnical Commission</name>
      <abbreviation>IEC</abbreviation>
      <uri>www.iec.ch</uri>
    </organization>
  </contributor>
  <edition>4</edition>
  <language>en</language>
  <language>fr</language>
  <script>Latn</script>
  <status>
    <stage>PUBLISHED</stage>
  </status>
  <copyright>
    <from>2013</from>
    <owner>
      <organization>
        <name>International Electrotechnical Commission</name>
        <abbreviation>IEC</abbreviation>
        <uri>www.iec.ch</uri>
      </organization>
    </owner>
  </copyright>
  <relation type="updates">
    <bibitem type="standard">
      <formattedref format="text/plain">IEC 60050-351:2006</formattedref>
      <docidentifier type="IEC" primary="true">IEC 60050-351:2006</docidentifier>
    </bibitem>
  </relation>
  <relation type="instanceOf">
    <bibitem type="standard">
      <fetched>2023-11-30</fetched>
      <title type="main" format="text/plain" language="en" script="Latn">International Electrotechnical Vocabulary (IEV) - Part 351: Control technology</title>
      <title type="main" format="text/plain" language="fr" script="Latn">Vocabulaire Electrotechnique International (IEV) - Partie 351: Technologie de commande et de régulation</title>
      <uri type="src">https://webstore.iec.ch/publication/194</uri>
      <uri type="obp">https://webstore.iec.ch/preview/info_iec60050-351{ed4.0}b.pdf</uri>
      <docidentifier type="IEC" primary="true">IEC 60050-351:2013</docidentifier>
      <docidentifier type="URN">urn:iec:std:iec:60050-351:2013-11:::</docidentifier>
      <date type="published">
        <on>2013-11-25</on>
      </date>
      <contributor>
        <role type="publisher"/>
        <organization>
          <name>International Electrotechnical Commission</name>
          <abbreviation>IEC</abbreviation>
          <uri>www.iec.ch</uri>
        </organization>
      </contributor>
      <edition>4</edition>
      <language>en</language>
      <language>fr</language>
      <script>Latn</script>
      <abstract format="text/html" language="en" script="Latn">IEC 60050-351:2013 gives the general terminology used in control technology, as well as general terms pertaining to specific applications and associated technologies. This new edition reviews and complements the previous one. It has the status of a horizontal standard in accordance with IEC Guide 108.</abstract>
      <abstract format="text/html" language="fr" script="Latn">L'IEC 60050-351:2013 comprend la terminologie générale ainsi que les terms généraux appartenant aux applications spécifiques de la technologie de commande et de régulation. Elle a le statut de norme horizontale conformément au Guide IEC 108.</abstract>
      <status>
        <stage>PUBLISHED</stage>
      </status>
      <copyright>
        <from>2013</from>
        <owner>
          <organization>
            <name>International Electrotechnical Commission</name>
            <abbreviation>IEC</abbreviation>
            <uri>www.iec.ch</uri>
          </organization>
        </owner>
      </copyright>
      <relation type="updates">
        <bibitem type="standard">
          <formattedref format="text/plain">IEC 60050-351:2006</formattedref>
          <docidentifier type="IEC" primary="true">IEC 60050-351:2006</docidentifier>
        </bibitem>
      </relation>
      <place>Geneva</place>
    </bibitem>
  </relation>
  <place>Geneva</place>
  <ext schema-version="v1.0.0">
    <doctype>international-standard</doctype>
    <editorialgroup>
      <technical-committee number="1" type="technicalCommittee">TC 1</technical-committee>
    </editorialgroup>
    <ics>
      <code>01.040.25</code>
      <text>Manufacturing engineering (Vocabularies)</text>
    </ics>
    <ics>
      <code>25.040.40</code>
      <text>Industrial process measurement and control</text>
    </ics>
    <structuredidentifier type="IEC">
      <project-number part="351">60050</project-number>
    </structuredidentifier>
    <price-code>iec:P</price-code>
  </ext>
</bibdata>

Notice that the instanceOf document is the exact same document (IEC 60050-351:2013), not the undated reference of (IEC 60050-351).

Questions:

  1. Is this useful in any way?
  2. Should the instanceOf point to the undated reference?
andrew2net commented 11 months ago

@ronaldtse If year is not specified in reference, a new undated instance is created. Dated version is added as a relation with instanceOf type. We have that behavior for all the flavor gems based on IsoBiblopgraphicItem.

  1. & 2. I think the feature is used in Metanorma, so we should ask @opoudjis.
opoudjis commented 11 months ago
  1. Is this useful in any way?

I don't care. It is the right thing to do, and I decided that 4 years ago.

Undated references are fictions concocted in the standards world, and only dated references are real: they are using the title of a Work to refer to a series of Works, of which the dated reference is a concrete instance. The dated reference is what can be dated and tracked down, and ISO bibliographic site descriptions of undated works always pointed to the latest dated instance as the concrete instantiation of the Work series.

Note that ISO for example discusses ISO-639 in the abstract in https://www.iso.org/iso-639-language-code as an undated Work, but when it comes to hyperlinking, it links

ISO 639, Code for individual languages and language groups, can be applied across many types of organization and situations

to the page for ISO 639:2023. There is no reason to think that a Relaton work would not eventually be expected to do something similar.

The instanceOf relation is not invoked in current Metanorma code. But I asked Andrej to put it there, because to throwing away useful retrieved data about the latest edition of an undated Work would be inane. Sooner or later, it will be needed, and not providing the dated version of the Work is asking for confusion and category errors.

  1. The behaviour of all relation[@type = '...Of'] relations, as Andrej indicates, is indeed that the child is the subject of the ...Of claim. RTFM: https://www.relaton.org/specs/model/relations/

instanceOf document B is an instance of document A (e.g. an edition, a format, a single copy: agnostic as to whether B is an Expression, Manifestation, or Item) ([inverse:] hasInstance)