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

Bibliographic date for "revision" is outside of Bibdata structure #30

Closed
ronaldtse opened this issue Dec 9, 2018 · 7 comments
Closed
Assignees
Labels
enhancement New feature or request

Comments

@ronaldtse
Copy link
Contributor

In Metanorma XML we have the revision date outside of the <bibdata> structure:

<version>
  <edition>1</edition>
  <revision-date>2018-09-10T00:00:00Z</revision-date>
</version>

This makes it impossible to know the revision (and other dates) of a document from the Relaton file, we need the Metanorma file to do that.

Should this information be available within <bibdata>?

@ronaldtse ronaldtse added the enhancement New feature or request label Dec 9, 2018
@opoudjis
Copy link
Contributor

opoudjis commented Dec 9, 2018

We left it outside of the bibdata out of a notion that the bibdata was describing the work and not the version. But that is overly scrupulous, I agree. Moving the version back into bibdata is going to require a lot of code changes.

I don't even remember where the relaton writeup is, but it is going to have to be updated in light of these changes.

@ronaldtse
Copy link
Contributor Author

The write up is at relaton-models. I believe we have bibdates within bibdata.

@opoudjis
Copy link
Contributor

opoudjis commented Dec 9, 2018

We do, but the revision date should be kept separate; it does not correspond to a distinct phase of document production, but applies across any of them.

@ronaldtse
Copy link
Contributor Author

Maybe what we need is to encode the revision dates in both — inside bibdata (the publication date) and also outside of it (as the generation date of document).

At the CalConnect standards repository we’re trying to make a page for each project like the ISO site, so if we can represent a Relaton object with multiple document revisions (at different stages), we can generate a page that show standards progression and also the drafts that come with each stage.

@opoudjis
Copy link
Contributor

If it's the publication date of the document, it's covered by the existing <date type="published">. Revision dates apply to pre-published documents; and publication dates of different editions should be covered as distinct related relaton descriptions. No, it's going to be simpler just to move the version tag inside bibdata.

The writeup is in fact in the ISO690 document. That document is going to have to be updated extensively.

@opoudjis
Copy link
Contributor

The representation of multiple document revisions in a single Relaton file is covered by relaton/relaton#19

@opoudjis
Copy link
Contributor

Following metanorma/metanorma-model-iso#15 (comment), edition is now in bibdata as a separate tag, and should be removed from the version tag.

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
None yet
Development

No branches or pull requests

2 participants