Andreas Sewe wrote:
> @ref, however, sounds like an entirely reasonable name for such an
> attribute.
>
I'm coming around to this view as well. On the downside, there are
implementations of the draft that are being prepared now, I will ping
the folks who I know are implementing and see if a na
Considering the above-mentioned symmetry with @href, I’m coming
around to whose-ever view it was that this attribute should be
called @ref for balance.
+1 for @ref as well.
Thomas Broyer <[EMAIL PROTECTED]>:
Sylvain Hellegouarch <[EMAIL PROTECTED]>:
I would rather move the content of that attribute as a text
element of the 'in-reply-to' element (as does the atom:id
element).
I raised a similar issue regarding James Snell's Feed Rank I-D where a
ranking:scheme
Apologies for cross-posts.
The full call is below (and at http://www2006.org/developers/cfp.php),
but in short we're looking for developers to present cool stuff. It
can be anything from a 5 min lightning demo to a 30 min presentation.
Of particular relevance here are the "Next Wave" sessions : a
* Martin Duerst wrote:
>When looking with a microscope, you will find some little
>differences, because xs:anyURI was described before the IRI
>spec (RFC 3987) was approved. These differences are:
>
>1) xs:aryURI also allows spaces and a few other ASCII characters
>that are not allowed in URIs
At 00:42 06/03/17, Norman Walsh wrote:
>/ "Thomas Broyer" <[EMAIL PROTECTED]> was heard to say:
>| RFC 3987 says (section 1.2 Applicability):
>|For example, XML schema [XMLSchema] has an explicit type
>|"anyURI" that includes IRIs and IRI references. Therefore, IRIs
>|and
