SV: [cam] Re: [ebxml-dev] cam examples

[Bryan Rasmussen <brs@itst.dk>]

Well I'm having trouble runing JCAM, it's not finding JDOM (which I had to
install for this), and anyway I'm not particularly interested in running
JCAM.

 I have to make a report as to what I think of CAM as a specification, not
what I think of JCAM as an implementation. 

I'm not particularly good at Java either, generally I'm competent enough to
install and run programs, I can do maintenance level coding in it, but it is
not my language of choice, so you see, I have no interest in JCAM and if I
were to recommend using CAM for anything I would probably also want to
implement it in some other language (my report however is not a report for
recommendation but rather a report on how the project currently stands)
I think as a general rule it is a good idea that specifications which deal
with such things as input formats to processes that should result in output
formats, that the expected output formats are also shown. That these outputs
are gotten by running a process through JCAM or that they're written by hand
is not important, but I think it's sort of a weird idea that people looking
at the spec and wondering what outputs look like should download an alpha
implementation and run it. Especially as that alpha implementation doesn't
seem to be referred to in the spec as a canonical implementation.

In other words, I was asked to take a look at CAM and make a report on it,
in order to do that I should do a lot of things other than run an
implementation to check outputs. This morning I've spent a couple hours on
downloading, installing, running command lines, and not getting any closer
to the knowledge I would like to complete my report. I can't help but think
that if other people find themselves in the same situation it might be
better if some examples outputs were included with the examples zip because
it seems like a hell of a lot of work for each person to replicate. 



 



-----Oprindelig meddelelse-----
Fra: David RR Webber [mailto:david@drrw.info]
Sendt: 13. august 2004 22:42
Til: Chiusano Joseph
Cc: Bryan Rasmussen; ebxml-dev@lists.ebxml.org; CAM
Emne: Re: [cam] Re: [ebxml-dev] cam examples


Bryan,

If you download the CAM tutorial ZIP file - it contains not just the PPT -
but
lots of CAM templates too - that's on the link at :
 
 http://www.oasis-open.org/committees/cam - and is a public file.

To obtain output samples - go to the jCAM site:

 http://www.jcam.org.uk 

and download the CAM processor itself - and run the samples.

Actually - if you just invoke the processor - you will get back all the
command-line options - there's a wealth of output selections to pick from.

Enjoy and thanks for your interest in CAM.

DW.

p.s. Joe - can you just "reply all" to this for me to post to ebXML-dev - as
     I don;t have "write-access" there!  Cheers, DW

Quoting Chiusano Joseph <chiusano_joseph@bah.com>:

> Forwarding to the CAM TC listserv for you.
> 
> Kind Regards,
> Joe
> 
> Bryan Rasmussen wrote:
> > 
> > Sorry to be asking this here, but the cam comments list strikes me as
> being
> > very lightly used and I'd like to get a response before the weekend so
> > hopefully this ups my chances.
> > 
> > skimming the cam specification I saw lots of examples of how cam
documents
> > should be structured, but I didn't notice any example of an output
> document,
> > if you know of any example cam instance, and the example xml content
that
> > comes out the other end I would appreciate it. I think I can see how
these
> > documents are supposed to be structured but I think it is much better to
> see
> > an example.
> > 
> > Or if you have a really simple cam example just using xml as its
taxonomy
> > (the addressExample.xml would be suitable for this) with an example
> output.
> 
> -- 
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz Allen Hamilton
> 
> To unsubscribe from this mailing list (and be removed from the roster of
the
> OASIS TC), go to
>
http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.php
.
> 
> 


http://drrw.net