W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > July 2001

Re: Priorities for F2F (completion of ACTION: 2001-06-22#4)

From: Graham Klyne <Graham.Klyne@baltimore.com>
Date: Mon, 16 Jul 2001 15:16:06 +0100
Message-Id: <5.0.2.1.2.20010716151110.035b6b30@joy.songbird.com>
To: Aaron Swartz <me@aaronsw.com>
Cc: w3c-rdfcore-wg@w3.org
At 01:34 PM 7/13/01 -0500, Aaron Swartz wrote:
>On Friday, July 13, 2001, at 01:22  PM, pat hayes wrote:
>>However, maybe I was wrong, but I have been assuming that 'literal' 
>>referred not only to <data:..> but also to things like <string:..> and 
>><integer:....>, ie data types more generally (??). If so, I think it 
>>wouldnt be correct to say that all of these only denote themsleves, eg 
>>something labelling an integer wouldn't actually be an integer.
>
>Well, while the current M&S doesn't deal with data-typing (AFAIK), "data:" 
>URIs do provide that function. It uses a MIME type to define the type of 
>the data. For example:
>
>         <data:literal/integer:10>
>         <data:literal/string:foo>
>
>But what makes you think that literal refers to these concepts? I don't 
>see anything like that in the spec.

Another data: point... to get literal/integer recognized as a MIME type 
would require a new IETF standards-track RFC, something that I don't think 
would be easily achieved for that particular idea.  A MIME subtype 
registration might give you something like:

     <data:text/literal-integer,10>

but I'm not sure if it's worth the effort.

#g


------------------------------------------------------------
Graham Klyne                    Baltimore Technologies
Strategic Research              Content Security Group
<Graham.Klyne@Baltimore.com>    <http://www.mimesweeper.com>
                                 <http://www.baltimore.com>
------------------------------------------------------------



-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
Received on Monday, 16 July 2001 10:51:46 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:38:10 EDT