search

rfc-format / draft-iab-xml2rfc-v3-bis

-bis document for the RFC format xml2rfc v3 draft
6 stars 10 forks source link

pn attribute #174

Closed mnot closed 3 years ago

mnot commented 3 years ago

The 2.32 revision of the schema changed the content of the pn attribute from text to an xsd:ID. This should be documented.

stpeter commented 3 years ago

It seems that the intent here might have been to disallow whitespace in the pn attribute, since the pn attribute is used in the same ways as the anchor attribute (but often auto-generated by tooling if the anchor attribute was not provided in the source file). But I agree that the change should be documented.

jrlevine commented 3 years ago

Sounds right, also makes it slightly clearer that pn's are supposed to be unique.

levkowetz commented 3 years ago

The uniqueness requirement was the primary reason for the change. One of the validators I used during development actually complained about pn not being xsd:ID ,:-)

stpeter commented 3 years ago

I suggest that we have consensus and this should be documented in 7991bis.

stpeter commented 3 years ago

@jrlevine Shall we close this (with the understanding that 7991bis will be updated as needed)? Whatever is best for your workflow...

jrlevine commented 3 years ago

OK with me

jrlevine commented 2 years ago

pn is in the RNG but is one of the generated elements excluded from the text. See #201