- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Thu, 20 Jan 2011 07:27:06 -0500
- To: Alan Ruttenberg <alanruttenberg@gmail.com>
- CC: nathan@webr3.org, "public-lod@w3.org" <public-lod@w3.org>
- Message-ID: <4D382A1A.3000105@openlinksw.com>
On 1/19/11 11:27 PM, Alan Ruttenberg wrote: > > > On Wed, Jan 19, 2011 at 11:11 AM, Kingsley Idehen > <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: > > On 1/19/11 10:59 AM, Nathan wrote: >> htTp://lists.W3.org/Archives/Public/public-lod/2011Jan/ - >> Personally I'd hope that any statements made using these URIs >> (asserted by man or machine) would remain valid regardless of the >> (incorrect?-)casing. > Okay for Data Source Address Ref. (URL), no good for Entity (Data > Item or Data Object) Name Ref., bar system specific handling via > IFP property or owl:sameAs :-) > > > Kingsley, same for you as Nathan. To what specification do you refer > to for the definitions and behavior of: > - "Data source address ref" > - Entity > - Statement. > > -Alan Alan, My response is purely about managing Identifiers that are used as functional unambiguous Name or Address References. Not quoting a W3C spec. Basically, expressing a view based on my understanding of what's practical. A system (e.g. a database or client app.) can (should) make a decision about how it handles resolvable Identifiers when used as Name or Address references. Kingsley > > > > > -- > > Regards, > > Kingsley Idehen > President& CEO > OpenLink Software > Web:http://www.openlinksw.com > Weblog:http://www.openlinksw.com/blog/~kidehen <http://www.openlinksw.com/blog/%7Ekidehen> > Twitter/Identi.ca: kidehen > > > > > > -- Regards, Kingsley Idehen President& CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Received on Thursday, 20 January 2011 12:27:37 UTC