Original text:
the cardinality of the relations.  The relations between the values of the attributes are explained in the interface sections.  The model shown in fig-ER-WKC models the contents of /.well-known/ core which contains: A link has the following attributes: <del> One or more link relations (expressed as space-separated values in the "rel" attribute, defaulting to "hosts").  They describe a </del>  relations between the link context and the link target. A link context URI ("anchor").  The link context defines the source of the relation, and serves as the Base URI for resolving <del> the target.  It can be relative, in which case it gets resolved against the Base URI of the ".well-known/core" document it was obtained from . It can be absent, in which the Base URI of the document is used as the context. </del>  A link target URI ("href", expressed between the angular brackets in link-format).  The link target defines the destination of the <del> relation, and is the topic of all other target attributes.  If it is a relative URI, it gets resolved against the link context URI. </del>  Other target attributes (eg. resource type (rt), interface (if), cor content-type (ct)).  These provide additional information copied from the value of the "hosts" relation and overwritten by the value of the con query parameter. <del> Links are modelled as they are in fig-ER-WKC.  As they do not have their ".well-known/core" document associated with them any more which would originally provide its Base URI, the "con" attribute of the registration fills that gap and is used as a Base URI. </del>  3.4.

Reviewer comments:
This is the first step to closing [54], doing the changes to the model itself. Won't close the issue by itself probably, as some other portions might mention the model. This does not try to address any of the open issues. [54]: URL
s taget/target/

Revised text:
the cardinality of the relations.  The relations between the values of the attributes are explained in the interface sections. <ins> Some of the attribute values are URIs.  Those values are always full URIs and never relative references in the data model.  They can, however, be expressed as relative references in serializations, and often are. </ins> The model shown in fig-ER-WKC models the contents of /.well-known/ core which contains: A link has the following attributes:  <ins> Zero or more link relations (expressed as space-separated values in the "rel" attribute, defaulting to "hosts").  They describe a </ins> relations between the link context and the link target. A link context URI ("anchor").  The link context defines the source of the relation, and serves as the Base URI for resolving  <ins> the target.  In the serialization, it can be relative, in which case it gets resolved against the Base URI of the ".well-known/ core" document it was obtained from . It can be absent, in which the Base URI of the document is used as the context. </ins> A link target URI ("href", expressed between the angular brackets in link-format).  The link target defines the destination of the  <ins> relation, and is the topic of all other target attributes.  In the serialization, if it is a relative URI, it gets resolved against the link context URI. </ins> Other target attributes (eg. resource type (rt), interface (if), cor content-type (ct)).  These provide additional information copied from the value of the "hosts" relation and overwritten by the value of the con query parameter.  <ins> Links are modelled as they are in fig-ER-WKC. </ins> 3.4.