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

references for joint publications #184

Closed
ogcscotts opened this issue Sep 3, 2020 · 12 comments
Closed

references for joint publications #184

ogcscotts opened this issue Sep 3, 2020 · 12 comments
Assignees
Labels
enhancement New feature or request

Comments

@ogcscotts
Copy link

How are references handled to documents published jointly by two organizations? For instance, many OGC standards have an ISO equivalent (which may be different dates); OGC and W3C publish several joint documents as well, but they have the same date.

@ronaldtse
Copy link
Contributor

@ogcscotts sorry I missed this.

In ISO 690:2020, we consider "joint published" (single document multiple publishers) and "dual-published" (multiple publications of the same content) separately. This is the relevant snippet.

image

A jointly published document is realized with 1 bibliographic item: a single document with 2 publishers.

A dual-published (should be "multi-published") document is realized with 2+ bibliographic items with independent publishers.

In this case, it seems that OGC/W3C documents are "jointly published", and OGC/ISO documents are multi-published.

This is tricky because OGC uses LNCS, which does not support this type of complex arrangement. Metanorma does not yet support these expressions.

@ronaldtse ronaldtse added enhancement New feature or request question Further information is requested labels Sep 17, 2020
@ogcscotts
Copy link
Author

@ronaldtse Thanks for the examples. You are correct in the nature of publications between OGC and W3C vs. ISO. Jointly published in LNCS can be fairly simple, just have the editor enter two publishers in the front of the entry; for dual, the editor will need to enter both documents as single entries, I suppose.

@ronaldtse
Copy link
Contributor

There is an issue here because the information about dual publishers isn't fetchable. We will have to enhance the reference source to provide this information.

@opoudjis
Copy link
Contributor

opoudjis commented Sep 4, 2023

ITU deals with this. Ensure that the span notation used to manually enhance referencs copes with dual publication requirement.

@opoudjis opoudjis self-assigned this Sep 4, 2023
@opoudjis opoudjis removed the question Further information is requested label Sep 4, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Metanorma Sep 4, 2023
@opoudjis
Copy link
Contributor

opoudjis commented Sep 4, 2023

Explore merging two relaton fetched records for the same document. Provide guidance about how to write such a reference from scratch, using span notation.

@ghobona
Copy link

ghobona commented Sep 4, 2023

OGC Staff briefed on 2023-09-04.

Just noting that OGC Abstract Specification Topic 21 is published jointly with ISO as ISO 19170-1:2020.

@opoudjis opoudjis moved this from 🆕 New to 🏗 In progress in Metanorma Sep 8, 2023
@opoudjis
Copy link
Contributor

So will implement in metanorma a merge of two publications in references, to realise joint publications:

*[ref1, merge(OGC 20-040r3, ISO 19170-1:2020)]

This will fetch both references, treat the first reference as the basis, and merge into it details of the other documents that are specific to publication (publisher, docidentifier). I will also need to ensure that relaton-render deals with this; publishers won't be an issue, but it will be taken by surprise by multiple primary docidentifiers.

I will also realise dual publications:

*[ref1, dual(OGC 20-040r3, ISO 19170-1:2020)]

This will be realised as the first publication being treated as basic, and the other publications appearing as separate publications in the same entry, as "also published as". The relation we have in relaton that captures that is one of

  • reproductionOf: "document B is a Manifestation of the same Expression as document A",
  • the narrower reprintOf: "document B is a reproduction of document A, involving a new publisher or distributor and mass dissemination, and no overriding concern with reproducing the source manifestation precisely (not necessarily restricted to print media)"
  • adoptedFrom : identical: "document A is adopted by a standards organisation from document B by a different organisation. (These are potentially the same content, but they have institutional authorship and application; this kind of appropriation of text is not characteristic of literary works.) document A is adopted from document B, without any change"

The slight problem is that our model assumes asymmetrical relations, that one SDO came first in this instance. I don't think this is that big a deal, but if we're going to call it "also published as", I'd be more comfortable with "reproductionOf", perhaps with a narrower qualification independentPublicationOf or dualPublicationOf.

@ronaldtse
Copy link
Contributor

@opoudjis I wonder if this is better served at the Relaton level, because Relaton needs to handle dual publications (as per ISO 690).

@opoudjis
Copy link
Contributor

opoudjis commented Sep 18, 2023

I wonder if this is better served at the Relaton level, because Relaton needs to handle dual publications (as per ISO 690).

relaton-render clearly needs to deal with a bibliographic reference that contains dual publication information, and that will be output as a merger of two relaton records.

But the notion that relaton, as a scraper of information from SDO websites, is going to have the slightest idea that a document is dual published, is one I find acutely implausible. And I am of course correct:

What needs to happen is <bibitem id="A">(Record 1) <relation type="reproductionOf"><bibitem id="B">(Record 2)</bibitem></relation></bibitem>. That's a relaton record merger. But it is not going to have anything to do with relaton screenscraping.

opoudjis added a commit to metanorma/metanorma-standoc that referenced this issue Sep 29, 2023
opoudjis added a commit to metanorma/metanorma-standoc that referenced this issue Sep 29, 2023
opoudjis added a commit to metanorma/metanorma.org that referenced this issue Sep 29, 2023
opoudjis added a commit to metanorma/metanorma-standoc that referenced this issue Sep 29, 2023
@opoudjis
Copy link
Contributor

Merge URIs as well as docidentifiers and publishers.

@opoudjis
Copy link
Contributor

relaton-render: Add Japanese i18n (although we currently have not resolved at, in.)

Restricting document identifiers to primary if present.

opoudjis added a commit to relaton/relaton-render that referenced this issue Sep 29, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Metanorma Sep 29, 2023
@ronaldtse
Copy link
Contributor

@opoudjis just a note that only certain Relaton flavors use screenscraping. For example OGC records do not come from screenscraping. Whether dual published information is available is a separate question.

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
Archived in project
Development

No branches or pull requests

4 participants