relaton / relaton-iana

Relaton for IANA references
MIT License
0 stars 0 forks source link

Individual registries should be citable #2

Closed ronaldtse closed 2 years ago

ronaldtse commented 2 years ago

We need to distinguish between:

In the current implementation at bibxml8, an IANA table is represented like this: https://xml2rfc.tools.ietf.org/public/rfc/bibxml8/reference.IANA.rpki.xml

This file represents an "IANA table” (in BibXML speak according to xml2rfc.tools.ietf.org). It actually represents an IANA page that provides a set of individual registries that belong to the same protocol.

For example, https://www.iana.org/assignments/rpki/rpki.xhtml is the "Resource Public Key Infrastructure (RPKI)” registry collection, it contains 7 individual registries: “ Registries included below • RPKI Signed Objects • RPKI Repository Name Schemes • rpki-rtr-pdu • rpki-rtr-error • BGPsec Capability • BGPsec_Path Flags • BGPsec Algorithm Suites “

Technically, a registry can be mandated by a different RFC.

We should make both types citable:

We need to update the Relaton IANA model and also the relaton-iana implementation.

andrew2net commented 2 years ago

@ronaldtse should we use for included registries collection's link and publish date?

ronaldtse commented 2 years ago

Yes for both. For each registry it also has a fragment anchor link, so let's use that one.

andrew2net commented 2 years ago

@ronaldtse some collections have included registries with id which conflicts with other registry. For example a collection ppspp has included registry with id message-types which conflicts with same named registry in a collection manet-parameters. Shouldn't we compose a cllection's id with included registry's id? For example papp-message-types and manet-parameters-message-types.

ronaldtse commented 2 years ago

Yes we should. But maybe not a - as the separator?

How about:

ronaldtse commented 2 years ago

I think a / makes more sense here.

andrew2net commented 2 years ago

@ronaldtse there are three collections that have registries without titles:

Shouldn't we skip these registries?

These two files are redirections to specific version:

What should we do with them?

ronaldtse commented 2 years ago

@ronaldtse there are three collections that have registries without titles:

Let's use the id= to be their title for now.

These two files are redirections to specific version:

We should ignore them.