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

Embedded documents in July 2004 CalConnect Interoperability Test Report #19

Closed
anermina opened this issue Dec 21, 2024 · 7 comments
Closed
Assignees
Labels
question Further information is requested

Comments

@anermina
Copy link
Collaborator

The July 2004 CalConnect Interoperability Test Report includes CalConnect I-III test reports at the paper's end. It seems these documents should be embedded; however, due to their uniform structure and the fact that they are three separate documents, our embed command is unsuitable in this case.

As an alternative, I used the include command, which resulted in clause numbering continuing throughout the paper.

Original (left) vs. generated (right):
image
image
image

Is the current encoding acceptable?

@anermina anermina added the question Further information is requested label Dec 21, 2024
@ronaldtse
Copy link
Contributor

@anermina there is no need to embed the documents, let’s just keep them separate. Thanks!

@ronaldtse
Copy link
Contributor

If the original 3 documents were not published separately, then we include them. If they were published separately, just list them in the bibliography and no need to embed.

@anermina
Copy link
Collaborator Author

anermina commented Jan 5, 2025

Thank you @ronaldtse !
They were not published separately, so I included them.

@ronaldtse
Copy link
Contributor

@anermina actually can we publish those as separate documents? Let's find a proper docnumber for them. They deserve to be separate. Thanks.

@anermina
Copy link
Collaborator Author

anermina commented Jan 8, 2025

What I have concluded from the CalConnect samples is that the document identifier is created as follows:

  • The first two digits of the ID represent the last two digits of the year when the document is published. For example, if the document was published in 2018, the first two digits of the ID are "18";
  • The last two digits of the ID correspond to the ordinal number of the document published that year. For example, if it is the second document published in 2018, the ID would be "1802".

Since no other documents were published in 2000, 2001, and 2002, I assigned the IDs 0001, 0101, and 0201 for these documents in 9ced4d3.

@ronaldtse
Copy link
Contributor

Thank you @anermina ! Done in #17 .

@ronaldtse
Copy link
Contributor

What I have concluded from the CalConnect samples is that the document identifier is created as follows:

  • The first two digits of the ID represent the last two digits of the year when the document is published. For example, if the document was published in 2018, the first two digits of the ID are "18";
  • The last two digits of the ID correspond to the ordinal number of the document published that year. For example, if it is the second document published in 2018, the ID would be "1802".

Since no other documents were published in 2000, 2001, and 2002, I assigned the IDs 0001, 0101, and 0201 for these documents in 9ced4d3.

This is exactly correct. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants