OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [coel] Structure of the COEL JSON documents

Well spotted David,

I do not have any code using those files.

A suggestion: You used to have a BCD-like identifier for each discrete entry, in this case something like 01010000 - would that work? It allows up to 99 per level.

Dr. Paul Bruton

Chadwick House, Birchwood Park, Warrington, WA3 6AE
Paul.Bruton@tessella.com, T: +44 (0)7557 916535
www.tessella.com    Registered in England No. 1466429

Please consider the environment and do not print this e-mail unless you really need to.

This message is commercial in confidence and may be privileged. It is intended for the addressee only. Access to this message by anyone else is unauthorised and strictly prohibited. If you have received this message in error, please inform the sender immediately. Please note that messages sent or received by the Tessella e-mail system may be monitored and stored in an information retrieval system.

From:        <david.snelling@uk.fujitsu.com>
To:        <coel@lists.oasis-open.org>
Date:        14/10/2015 10:10
Subject:        [coel] Structure of the COEL JSON documents
Sent by:        <coel@lists.oasis-open.org>



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]