search

hassanakbar4 / tractive-test

0 stars 0 forks source link

The 3GPP reference bibxml can't be used #160

Closed hassanakbar4 closed 3 years ago

hassanakbar4 commented 11 years ago

component_Version 2 cli resolution_fixed type_defect | by magnus.westerlund@ericsson.com

The 3GPP reference files available at: http://xml.resource.org/public/rfc/bibxml5/ can't be used with version 2. However, to my understanding this is a result of the new version actually following the XML anchor syntax rules, which doesn't allow initial numbers. The old tool was lenient here and didn't care.

This is a migration issue as I see someone needs to create a new bibxml for 3GPP that uses anchors that doesn't start with 3GPP, and in addition keep both version alive for quite some time while people transit their source files to use the new anchor style.

I don't see being lenient helps that much, as basic XML tools also see the anchors as syntax violation.

Issue migrated from trac:160 at 2021-10-20 18:04:04 +0500

hassanakbar4 commented 11 years ago

@{"email"=>"arusso@amsl.com", "name"=>nil, "username"=>nil} commented

Just a confirmation of what Magnus reported -- v2 does not allow an anchor that starts with a numeral. Not only will 3GPP references from the citation library give the error "Syntax of value for attribute anchor of reference is not valid", but also any other anchor that begins with a numeral. For example, generating references such as the following would not be possible using v2. (They are from RFC 6144 and RFC 6782, respectively).

   [6NET]     6NET Consortium, "6NET", <http://www.6net.org/>.

   [464XLAT]  Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
              Combination of Stateful and Stateless Translation", Work
              in Progress, September 2012.
hassanakbar4 commented 11 years ago

@{"email"=>"tony@att.com", "name"=>nil, "username"=>nil} changed status from new to assigned

hassanakbar4 commented 11 years ago

@{"email"=>"tony@att.com", "name"=>nil, "username"=>nil} changed owner from henrik@levkowetz.com to tony@att.com

hassanakbar4 commented 11 years ago

@{"email"=>"tony@att.com", "name"=>nil, "username"=>nil} changed status from assigned to closed

hassanakbar4 commented 11 years ago

@{"email"=>"tony@att.com", "name"=>nil, "username"=>nil} changed resolution from ` tofixed`

hassanakbar4 commented 11 years ago

@{"email"=>"tony@att.com", "name"=>nil, "username"=>nil} commented

I modified the bibxml generation tools to create bibxml5 reference files using the name SDO-3GPP.xyz as the anchor name. I left the existing 3GPP files alone.

This should not have been allowed in the past. However, if we add aliases to xml2rfc, we might consider allowing something other than an XML ID to be used in some fashion. (I don't know if that is possible.)