Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PV, CR, Metrologia citations #145

Closed
Tracked by #157
opoudjis opened this issue Jul 13, 2021 · 19 comments
Closed
Tracked by #157

PV, CR, Metrologia citations #145

opoudjis opened this issue Jul 13, 2021 · 19 comments
Assignees
Labels
enhancement New feature or request

Comments

@opoudjis
Copy link
Contributor

How are they to be formulated, and rendered, in BIPM?

Comes from #133

@opoudjis opoudjis added the enhancement New feature or request label Jul 13, 2021
@opoudjis opoudjis self-assigned this Jul 13, 2021
@opoudjis opoudjis added this to Needs triage in Nick Nicholas via automation Jul 13, 2021
@ronaldtse
Copy link
Contributor

ronaldtse commented Jul 13, 2021

@opoudjis opoudjis moved this from Needs triage to High priority in Nick Nicholas Jul 13, 2021
@ronaldtse
Copy link
Contributor

@opoudjis opoudjis moved this from High priority to Current in Nick Nicholas Jul 13, 2021
@opoudjis opoudjis moved this from Current to On hold in Nick Nicholas Jul 26, 2021
@opoudjis
Copy link
Contributor Author

Pending implementation of relaton-bipm tickets.

@opoudjis opoudjis moved this from On hold to Needs triage in Nick Nicholas Sep 28, 2021
@opoudjis opoudjis moved this from Needs triage to Current in Nick Nicholas Sep 28, 2021
@opoudjis
Copy link
Contributor Author

So representative citation renderings are:

  • CR, 78
  • Metrologia, 1972, 8, 36
  • PV, 48, 24

The PV are Proceedings of the CIPM, and those are cited by volume and page number. So PV, 48, 24 is BIPM CIPM48, p. 24.

Metrologia is cited by year, volume, and page. So Metrologia, 1972, 8, 36 is BIPM Metrologia 8, p. 36.

CR are the Proceedings of the CPGM, and in the BIPM they are cited only by page number:

  • CR, 104 is Resolution 5 of the 13th CPGM.
  • CR, 100 is Resolution 3 of the 16th CPGM.

And that is because, horrifically, the "CR" volume number is given either in preceding prose, or implicitly. So:

1st CGPM, 1889

  • Sanction of the international prototypes of the metre and the kilogram (CR, 34 - 38)

That "(CR, 34 - 38)" is actually <<ref,page=34-38>>, where ref is BIPM CGPM01 (or possibly BIPM CGPM01 34 to BIPM CGPM01 38, if the citations in relaton are by page. The problem is, that the rendering of the volume number is left out in the current rendering.

Similarly, "the 16th CGPM (1979, Resolution 3, CR, 100 and Metrologia, 1980, 16, 56)" has "CR, 100" as the citation, but what is actually cited is BIPM CGPM16 100. Again, the volume is outside of the citation: "the 16th CGPM (1979,...".

In reality, the citation is of the Resolution, and not of the page. But this citation convention is so discursive, I'm not convinced it can be maintained.

@opoudjis
Copy link
Contributor Author

We have an additional problem with the current encoding of references in relaton-bipm:

BIPM CIPM, CIPM CPGM, and BIPM Metrologia all require parts in their references: "BIPM Metrologia 29 6 373", "BIPM CGPM01 1", "BIPM CIPM101 1".

We do not know those parts from the citations: the citations all go straight from volume number to page. Requiring the parts in the citations is simply not going to work. We need to be able to make citations without the part numbers, and (presumably) have the relaton-bipm database work out which file corresponds to a given page number.

@opoudjis opoudjis moved this from Current to On hold in Nick Nicholas Oct 1, 2021
@opoudjis
Copy link
Contributor Author

opoudjis commented Feb 12, 2022

If we are going to have machine parsed citations, we are going to have machine processed renderings of citations. I am not going to indulge the pointless abbreviation of dropping volume numbers.

Implementing CR and PV rendering, boldfacing the volume. We don't have Metrologia citations yet.

I will eventually assign the task to editors of making all the references in BIPM machine readable (including supplying the implicit volume numbers). But that is premature, as only CR is working currently.

@ronaldtse
Copy link
Contributor

ronaldtse commented Feb 12, 2022

Instead of "volume" I think you mean dropping "tome" numbers, because that number is not available in the data? The point of dropping that number is to make referencing possible, not "pointless" dropping. If you have it, use it. If not, skip it.

@opoudjis
Copy link
Contributor Author

opoudjis commented Feb 13, 2022

By "tomb", you mean "tome", which is French for "volume", I'm assuming. :)

When the proceedings of the first conference are discussed in the BIPM brochure appendix, the citation to the proceedings is given as CR, pagenumber. The reason the volume number is skipped is, it is implicit in the context --- this is the first conference, so it is supposed to be obvious to the reader that the page number belongs to volume 1.

What I am saying is, (a) we are going to have to add the volume number in to the crossreference anyway, to make any machine readable reference work, and (b) I don't think we should be then suppressing the volume number from rendering, because I think the BIPM convention of dropping volume numbers when they should be obvious from context is counterproductive. It's the kind of thing you would see in the 19th century, in the world of "op. cit." We shouldn't perpetuate it.

@ronaldtse
Copy link
Contributor

Thanks for the correction, which is better than my phone's autocorrect...

The point of dropping tome is that the resolutions/decisions are supposed to be individually referencable as resolutions/decisions, not as part of proceeding volumes. These objects will be directly available on the internet without any indication of which "tome" they were originally from.

i.e. in the digital age we don't care about tome -- these resolutions/decisions will be directly linked to the number of the meeting/conference.

opoudjis added a commit to metanorma/metanorma-bipm that referenced this issue Feb 13, 2022
@opoudjis
Copy link
Contributor Author

Well we don't support that yet anyway. The references right now only work to the level of volumes: we have page numbers in the citations, we don't have the means to map those to resolutions.

If you want to reference resolutions and not pages in the underlying machine readable encoding, and just display the page numbers in the rendering, that... is different again. But right now, we can't support what you're saying.

@ronaldtse
Copy link
Contributor

@metanorma/editors now all the PV and CR can be cited via Relaton. Can you please help update them soon? Thanks.

@anermina
Copy link
Contributor

After citations were added for PV and CR, @manuel489 helped generate the output with the latest release of relaton-bipm (1.11.0). Example is shown below. Is this expected output?
image

@opoudjis
Copy link
Contributor Author

opoudjis commented May 5, 2022

In fact, the CR and PV citations are meant to be hidden, for the purposes of the Brochure: they are implicit citations. I'll take care of that.

@ronaldtse
Copy link
Contributor

@opoudjis are we waiting for something here? BIPM is eager to finish this work. Thanks.

@opoudjis
Copy link
Contributor Author

Hiding the CR, PV citations. Should be straightforward.

@opoudjis
Copy link
Contributor Author

As enhancement: enforce implicit_reference at Presentation XML level, current code is not doing so.

@opoudjis
Copy link
Contributor Author

Implemented now the editors have to look up the individual CGPM Resolution and CIPM Decision reference tags, but the hiding references tag is done, so all necessary infrastructure should be in place. Ticket to close when they're done with it.

@ronaldtse
Copy link
Contributor

ronaldtse commented May 30, 2022

Related to metanorma/metanorma-bipm#164

@opoudjis
Copy link
Contributor Author

Superseded by #169

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Nick Nicholas
  
On hold
Development

No branches or pull requests

4 participants