[iri] #85: Align terminology in 3987bis with 3536bis

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[iri] #85: Align terminology in 3987bis with 3536bis

Peter Saint-Andre-2
<hat type='individual'/>

I think it makes sense to align 3987bis with RFC 6365 (BCP 166), or
preferably just to point to the latter specification wherever possible,
thus defining only IRI-specific terms in 3987bis.

Peter

--
Peter Saint-Andre
https://stpeter.im/



Reply | Threaded
Open this post in threaded view
|

Re: [iri] #85: Align terminology in 3987bis with 3536bis

Peter Saint-Andre-2
Still as individual...

On 11/11/11 5:08 PM, Peter Saint-Andre wrote:
> <hat type='individual'/>
>
> I think it makes sense to align 3987bis with RFC 6365 (BCP 166), or
> preferably just to point to the latter specification wherever possible,
> thus defining only IRI-specific terms in 3987bis.

I've taken another look at this.

3987bis defines the following terms (in alpha order):

character
character encoding
character repertoire
charset
create (a URI or IRI)
generate (a URI or IRI)
octet
IRI reference
IRI scheme
LEIRI
parsed IRI component
parsed URI component
protocol element
running text
sequence of characters
sequence of octets
UCS

Of those terms (or closely-aligned terms), the following are defined in
RFC 6365:

character
character encoding form
character encoding scheme
charset
protocol elements
repertoire
UCS-2 and UCS-4

I propose that we point to RFC 6365 for the latter terms and that we
make slight modifications to 3987bis for consistency with RFC 6365
(change "UCS" to "UCS-2 and UCS-4" or just "UCS-4" as appropriate,
change "character encoding" to "character encoding form" or "character
encoding scheme" as appropriate, etc.).

Peter

--
Peter Saint-Andre
http://stpeter.im/