Article

[Patrick Durusau <patrick@durusau.net>]

Eric,

I have what may seem like a silly question but here goes:

Who is the intended audience for the article?

I ask because the long stretch of UML diagrams makes me suspect it isn't
managers or users. 

Starting with figure 2 where *the usage of each of the properties* is
explained.

Even if the purpose of the article is to interest even information
architects or programmers in the JPA/ICOM framework, it doesn't have to
explain every property or its usage. 

Sure, a reference manual or standard has to do that, but not an article
meant to interest others in its use.

A more compelling case could be made with fewer diagrams.

For example, surely there are use cases that Oracle is already working
on using ICOM. Where integration has resulted in a benefit to the
organization.

Why not start with a very high level view of that problem and walk
through a very simplified version of ICOM?

For example, Entity represents XXX and just mentioned that all entities
have access controls (for details see the ICOM standard), etc. 

I would suggest also block diagramming, at a fairly high level, what JPA
brings to ICOM.

Hope you are having a great day!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau
Newcomb Number: 1