metanorma / pubid-ieee

PubID spec and implementation for IEEE deliverables
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

Clarification request for identifiers published date, draft date, edition date. #116

Closed mico closed 1 month ago

mico commented 3 months ago

For drafts we have date: IEEE Draft Std P802.1AX-REV/D4.0, March 2014 But also we have date for identifiers with ISO stage, like: IEEE Unapproved Draft Std P12207/FDIS, Nov 2007 Sometimes without stage or draft but it have date: IEEE/IEC P60076-57-1202, July 2014 Sometimes there are just year: IEEE Std 1491-2012 Also we have edition date I didn't mentioned: IEC 61691-7 Edition 1.0 2009-12

Is the draft date and identifier with ISO stage (now considered as draft) are the same? When identifier without draft or stage have date is it publication date? Publication date and draft date are not the same, right? And all these are not related to edition date?

Currently for IEEE we have:

ronaldtse commented 3 months ago

For drafts we have date: IEEE Draft Std P802.1AX-REV/D4.0, March 2014

The draft date is actually the publication date of the draft.

But also we have date for identifiers with ISO stage, like: IEEE Unapproved Draft Std P12207/FDIS, Nov 2007

Let's use a proper ID of:

IEEE Unapproved Draft Std P12207/DFDIS, Nov 2007

I remember Patrick Gibbons says that if there is "Draft", don't write "Std" (#107) ?

Sometimes without stage or draft but it have date: IEEE/IEC P60076-57-1202, July 2014

The proper ID is:

IEEE/IEC P60076-57-1202/D{draft id}, July 2014

We just don't know what {draft id} is

Sometimes there are just year: IEEE Std 1491-2012

Publication date is "2012".

Also we have edition date I didn't mentioned: IEC 61691-7 Edition 1.0 2009-12

Edition is "1.0". Publication date is "2009-12".

Is the draft date and identifier with ISO stage (now considered as draft) are the same?

What do you mean? I don't understand this question.

When identifier without draft or stage have date is it publication date?

Yes.

Publication date and draft date are not the same, right?

Actually, every document only has 1 date, which is the date this document is "offered".

published document => has publication date, which is also edition date. draft document => has draft date.

mico commented 3 months ago

IEEE/IEC P60076-57-1202/D{draft id}, July 2014

@ronaldtse Does it means that when we have date in identifier, like ", July 2014" at the end, it is draft, right? But when we have only year as in identifier IEEE Std 16085-2020 that doesn't mean it's draft, is it correct?

Also we have edition date I didn't mentioned: IEC 61691-7 Edition 1.0 2009-12

Edition is "1.0". Publication date is "2009-12".

Should we reformat it as IEC 61691-7 Edition 1.0, December 2009?

Is the draft date and identifier with ISO stage (now considered as draft) are the same?

What do you mean? I don't understand this question.

Identifiers with ISO stage usually also have publication date, should it be considered as "draft date"?

Actually, every document only has 1 date, which is the date this document is "offered".

published document => has publication date, which is also edition date. draft document => has draft date.

Should we use only "publication date" for any types of dates like edition date, draft date, publication date? Now edition date, publication date and draft date are different attributes.

opoudjis commented 3 months ago

I'm coming in to this with little context, but, to confirm:

But also we have date for identifiers with ISO stage, like: IEEE Unapproved Draft Std P12207/FDIS, Nov 2007

Yes, that is a draft date, since it is the date of publication of a draft of a document, and the identifier is explicitly saying that.

It is usual for the date of publication of a document to be year, and the date of draft to be month or even month and day; that's because you can have many drafts of a document issued in a year, but I don't think I've seen a case where there are two different publications/editions of a document in a year.

That said, BSI we have cases where some classes of document include the month in a publication date, and some do not. I really think you should only infer draft vs publication status of a document from whether the document is said to be a date. Yes, I would be surprised if a month is given for a publication date, but it is not impossible: BSI does it.

Should we use only "publication date" for any types of dates like edition date, draft date, publication date? Now edition date, publication date and draft date are different attributes.

Like I said: there's a reason bibliographic entries differentiate them, but I would be very surprised if any standards identifier uses more than one date. Drafts don't have a publication date. Published documents don't care in their identifier about draft dates. Edition dates usually override first publication dates. The only case where we routinely see two dates is in amendments and corrigenda, where you have a date of publication of the original document, vs a date of publication of the amendment.

Only model these as different dates if you have an identifier that uses two of them, or if the formatting requirements are different. The month status of drafts, I think, is inherited from the document being a draft, not from the date being differently formatted.

ronaldtse commented 3 months ago

What @opoudjis states is correct.

IEEE/IEC P60076-57-1202/D{draft id}, July 2014 @ronaldtse Does it means that when we have date in identifier, like ", July 2014" at the end, it is draft, right? But when we have only year as in identifier IEEE Std 16085-2020 that doesn't mean it's draft, is it correct?

The "Pxxxx" and "/D..." tells us it's a draft, because IEEE drafts are published by projects "Pxxxx" and (most) have a draft number ("/D...").

", July 2014" only tells us the "date" (publication date or draft date) of this document.

When we have "IEEE Std 16085-2020", which contains "Std", means it's not a draft. See #26 .

Also we have edition date I didn't mentioned: IEC 61691-7 Edition 1.0 2009-12 Edition is "1.0". Publication date is "2009-12". Should we reformat it as IEC 61691-7 Edition 1.0, December 2009?

That's fine with me, because this is IEEE style.

Is the draft date and identifier with ISO stage (now considered as draft) are the same? Identifiers with ISO stage usually also have publication date, should it be considered as "draft date"?

As @opoudjis mentioned. Do we have cases where a document identifier have both "draft date" and "publication date"? If not, PubID-IEEE doesn't need to handle that case.

We just handle 1 date. It is up to the user to determine whether it is a publication date or a draft date.

Actually, every document only has 1 date, which is the date this document is "offered". published document => has publication date, which is also edition date. draft document => has draft date. Should we use only "publication date" for any types of dates like edition date, draft date, publication date? Now edition date, publication date and draft date are different attributes.

Do you think we can just use 1 "date" to handle? Unless we have multiple dates in one PubID?

mico commented 3 months ago

Do you think we can just use 1 "date" to handle? Unless we have multiple dates in one PubID?

@ronaldtse My question is more about, did I make a mistake using 3 different dates for draft, edition, and publication? I'm fine with all them using separate attributes, but maybe separate attributes for draft date and publication date are too much?

ronaldtse commented 3 months ago

@mico its not a mistake per se but it’s difficult to determine the type of date accurately in the identifier, and hence difficult to use. Better stick with one date.

opoudjis commented 2 months ago

Does this ticket need to stay open, @mico?

mico commented 2 months ago

Unless we have multiple dates in one PubID?

IEC/IEEE 62582-1:2011 Edition 1.0 2011-08

This should be converted to IEEE format, then it will be IEC/IEEE Std 62582-1-2011 Edition 1.0 2011-08 Twice mentioned the same year.

image

Year 2011 was the part of identifier but later on it was removed. I'm not sure how to approach this case. Could anything from these work?

opoudjis commented 2 months ago

So in IEC/IEEE Std 62582-1-2011 Edition 1.0 2011-08 (wherever the hell that came from), there is a year date for the standard, and a year + month date for the edition. They are not in fact different years, they are different granularities of the same year, and if the next edition were published in May 2024, it would turn into IEC/IEEE Std 62582-1-2024 Edition 2.0 2024-05. You are not going to get IEC/IEEE Std 62582-1-2011 Edition 2.0 2024-05, that is not how those dates work. The dates in fact indicate the edition in ISO practice (which IEC inherits), and the edition date is merely an elaboration of that.

IEC/IEEE Std 62582-1-2011 Edition 1.0 2011-08 seems to me to be preferable to the last two alternatives, but it is your job to investigate IEEE possible identifier formats: I have no idea what IEEE expect to see, and I don't have access to any more information than you do via Google. I am not willing to make stuff up that a client will turn around and tells us is wrong.