W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005


From: Andrzej Zydron <azydron@xml-intl.com>
Date: Thu, 16 Jun 2005 10:16:13 +0100
Message-ID: <42B1435D.2020909@xml-intl.com>
CC: public-i18n-its@w3.org

Hi Felix,

CAM is certainly very heavy going! One of the major problems is the 
original documentation which is quite impenetrable, and I have not yet 
found a decent article about it on the web. A better introduction to CAM 
can be found in the executive summary document: 

In addition it is worth downloading the following:


and looking at the Power Point presentation "Introducing CAM - Tutorial.ppt"

My understanding of CAM is that it provides a detailed and flexible 
vocabulary describing how to process a given XML document. It contains 
predicates such as:

makeOptional(), makeMandatory()
makeRepeatable(), setLimit()
startBlock(), endBlock()

The Content Reference rules are of particular interest to us as are the 
conditional expressions. It also uses standard XPath expressions.

It worth looking at a sample CAM template such as:


CAM is not just about NOUN definitions. CAM can define 
BusinessUseContext rules, DataValidations, ContentReference rules as 
well as Assembly structures. All very powerful and flexible.

My current understanding (still incomplete) of CAM is that it should 
provide a sufficient vocabulary to be able to describe semantically the 
requirements for http://esw.w3.org/topic/its0505Translatability, 
http://esw.w3.org/topic/its0505WordCount and possibly provide a 
mechanism for http://esw.w3.org/topic/its0505LimitImpact. It would do 
this via an external CAM XML definition document that would be 
applicable to a given DTD/XSD type, and/or individual document instance. 
This decouples the problem of an ITS tag set for the above topics from 
embedding and the intendant problems.

I need to spend a lot more time with CAM before I could say for certain 
whether it would be a viable solution, but there appear to be some very 
good things within the CAM specification that are worth investigating 

Best Regards,


Felix Sasaki wrote:
> Hi Andrzej,
> I had a look at CAM [1] which you talked about yesterday at the telecon. 
> It seems to be that it CAM is made for the augmentation of schemas with 
> additional information. One kind of information can be used to describe 
> the relations of element and attribute names from different namespaces 
> to an external knowledge base of names, in the CAM terminology "nouns". 
> I'm not sure if that solves our problems, for example to avoid impact of 
> ITS on existing markup schemes and documents, e.g. problems with XPath 
> etc. What we need is a way to describe the relations of markup A from 
> namespace to markup from namespace B, to be able to say s.t. "For this 
> processing step,  IMAGINE that <html:span> is equal to <its:span>." With 
> CAM, this seems to be possible through the "nouns" knowledge base, and 
> there seems to be no mechanism to process "IMAGINE". Also it seems that 
> there is not very much happening in the TC, the spec. was from 2004, and 
> i didn't found many implemenations / applications.
> I just had a quick look into this, so maybe my impression is wrong that 
> this doesn't solve our problems. What do you think? Do you have more 
> material?
> Best, Felix.
> [1] /www.*oasis*-open.org/committees/tc_home.php?wg_abbrev=*cam*/


email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
	PO Box 2167
         Gerrards Cross
         Bucks SL9 8XF
	United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.
Received on Thursday, 16 June 2005 09:16:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:04 UTC