-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
@anermina there is no need to embed the documents, let’s just keep them separate. Thanks! |
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. |
Thank you @ronaldtse ! |
@anermina actually can we publish those as separate documents? Let's find a proper docnumber for them. They deserve to be separate. Thanks. |
What I have concluded from the CalConnect samples is that the document identifier is created as follows:
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! |
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, ourembed
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):
Is the current encoding acceptable?
The text was updated successfully, but these errors were encountered: