[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Structure of the COEL JSON documents
Folks, As happens when you finally start working on something you find the bugs in the idea. Here is a typical entry from the class file: {"class_id": 1, "code": 4352, "cluster_id": 1, "name": "Body"} The cluster_id points to the cluster_id for the parent of this class and the class_id is used similarly in the sub-class file. The I have problem is with the code. It is currently created as a cluster code time 4096 plus the class ode * 256. Basically allowing only 15 classes, sub-classes, and element under each parent. The BAP currently allows for 99 of each. Furthermore the code fully encodes the hierarchy, so in some sense the _ids are redundant. I would like to have a go at a better extraction of this data from my database. It shouldn't take long and I do it tonight. But it means a slight delay to this work. Is there any implementation work built on the files currently posted in OASIS? I know the 'C' runs of the direct extract from the database, so it is not affected. -- Take care: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Senior Research Fellow Research Transformation and Innovation Fujitsu Laboratories of Europe Ltd. +44-7590-293439 (Mobile)
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]