Re: TM/JSON first draft

Hi Robert,

[...]
>> * It's unclear to me why the keys have sometimes a meaning (i.e.
>>   "movie" or "person" which indicates the type of a topic) and
>>   sometimes not (like "publication-year" which represents not the type
>>   of the occurrence). In the latter case, the key defines simply a
>>   container for an occurrence or a name.

> Actually "publication-year" is pretty meaningful in my book.

Yes, but it's a container which has no relevance in terms of Topic
Maps. But I understand now why you introduce the artificial keys.

[Verbosity]
> It can be authored by humans, but it is not what it is made for. It  
> is more likely that an existing document is parsed, then the  
> structure is altered or augmented, then json encoded and sent back.

I see. Maybe it would make sense to introduce prefixes and QNames to
make TM/JSON less verbose, though. This is actually a feature of
TM/XML which reduces the size of a topic map considerably.

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

<http://www.topicmaps.de/mailinglist/> German Topic Maps mailing list
<http://tinytim.sourceforge.net/> Open Source Topic Maps engine
<http://mappa.semagia.com/> Mappa - Python Topic Maps engine