Re: [xml2rfc-dev] putting page ranges into references, was: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-10#section-3.1.21

[Sandy Ginoza <[e-mail]>]

> On Nov 1, 2019, at 11:10 AM, Julian Reschke <[e-mail]> wrote:
> 
> On 01.11.2019 18:47, Sandy Ginoza wrote:
>> Is it correct that this mail refers to the following use of <seriesInfo>?
> 
> Nope. This mail thread was about how RFC 7991 tries to re-purpose
> seriesInfo to also control the metadata for the document itself.
> 
> (adjusting subject line)

Ack - thanks for the clarification. 

> 
>>           <seriesInfoname="Cryptology and Network Security"value="pp.
>> 142-157"/>
>> 
>> Is there a preferred handling here?  Annotation?  The output is slightly
>> different when using <annotation>.
>> 
>> Using <seriesInfo> (published):
>> 
>>    [Oreo]     Berkman, O., Pinkas, B., and M. Yung, "Firm Grip
>>               Handshakes: A Tool for Bidirectional Vouching", Cryptology
>>               and Network Security pp. 142-157, 2012.
> 
> I would say using seriesInfo for this would be an abuse of the element.
> 
>> Using <annotation>:
>> [Oreo]
>>    Berkman, O., Pinkas, B., and M. Yung, "Firm Grip Handshakes: A Tool
>>    for Bidirectional Vouching", 2012. Cryptology and Network Security
>>    pp. 142-157.
> 
> Yes, <annotation> adds text to the end.
> 
> There <refcontent> (see
> <https://greenbytes.de/tech/webdav/rfc7991.html#element.refcontent>).
> However, RFC 7991 fails to state where it goes (before or after
> <seriesInfo>). I believe xml2rfc puts it before, which doesn't help you
> here.
> 
> See <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/78>.

Ah, I totally missed <refcontent>.  Thanks for highlighting this!

Sandy 


> 
> Best regards, Julian
>