W3C home > Mailing lists > Public > www-tag@w3.org > October 2004

Re: Towards a position of neutrality on issue httpRange-14 for AWWW

From: Stuart Williams <skw@hp.com>
Date: Thu, 21 Oct 2004 16:29:51 +0100
Message-ID: <4177D5EF.30308@hp.com>
To: Norman Walsh <Norman.Walsh@Sun.COM>
Cc: www-tag@w3.org


Patrick was quoting from the October 19th draft and was suggesting a 
further change.
I was saying that it was a change I could live with. I can also live 
with the text in the Oct 19th draft too...  though there are two 
techniques described there... 1) concatenation 2) the practice of using 
namespace names that end in '#'. The '"This" in "This technique" may 
refer to either or both.


Norman Walsh wrote:

>/ Patrick.Stickler@nokia.com was heard to say:
>|> -----Original Message-----
>|> From: ext Stuart Williams [mailto:skw@hp.com]
>|> I'd like to support the edit you suggest. Norm was actioned to revise 
>|> this text to remove an actual error that intimated that RDF actually 
>|> introduced '#' during the concatenation process [1]. Your replacement 
>|> edit could fall within the scope of that action.
>|> [1] http://www.w3.org/2004/10/18-tagmem-irc#T19-59-57
>| Great.
>This has, in fact, already been completed. It's reflected in the 19
>October[1] draft:
>  For flat namespaces, concatenation is one useful mapping. If
>  namespace URIs that end with a hash (\u201c#\u201d) are chosen, then
>  simple concatenation of the namespace URI and the local name creates
>  a URI for a secondary resource (the identified term). This technique
>  is used for many [RDFXML] namespaces.
>  Other mappings are likely to be more suitable for hierarchical
>  namespaces; see the related TAG issue abstractComponentRefs-37.
>                                        Be seeing you,
>                                          norm
>[1] http://www.w3.org/2001/tag/2004/webarch-20041019/
Received on Thursday, 21 October 2004 15:30:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:06 UTC