W3C home > Mailing lists > Public > public-rdf-wg@w3.org > April 2011

Re: [JSON] JSON Serializations Lineup (ACTION-20)

From: Peter Frederick Patel-Schneider <pfps@research.bell-labs.com>
Date: Tue, 5 Apr 2011 11:36:09 -0400
Message-ID: <20110405.113609.75445533810574947.pfps@research.bell-labs.com>
To: <tomac@google.com>
CC: <public-rdf-wg@w3.org>, <hannes@muehleisen.org>
From: Thomas Steiner <tomac@google.com>
Subject: Re: [JSON] JSON Serializations Lineup (ACTION-20)
Date: Tue, 5 Apr 2011 10:24:55 -0500

>> Hmm.   How are the new names determined?
> Please see here:
> http://code.google.com/p/linked-data-api/wiki/API_Formatting_Graphs#Mapping_RDF_Property_URIs_to_JSON_Object_Properties

> 
> --Tom

I see several problems with this:

0/ # the short name for the property, as described in the property paths
   # section, if it has one 

   I don't see any section in the document whose label contains "path".

1/ # the rdfs:label of the property, if it is a legal short name for a
   # property that doesn't clash with an existing name  

   The rdfs:label may not be unique.  
   What is an existing name?
   How does one determine the order in which to do this?

2/ # the local name of the property (the part after the last hash or
   # slash),  if it is a legal short name for a property that doesn't
   # clash with an existing name  

   How does one determine the order in which to do this?

3/ # the prefix associated with the namespace of the property (the part
   # before the last hash or slash), concatenated with an underscore,
   # concatenated with the local name of the property  

   There may be no such prefix.


peter
Received on Tuesday, 5 April 2011 15:36:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:41 GMT