RE: Re[2]: [cgmo-webcgm] Did we miss something?

["DULUC, Franck" <franck.duluc@airbus.com>]

Benoît,

see below

> I'm not sure I totally understand, so let me ask a few questions if I
> may.

> yes, the 'name' attribute will be available using the DOM, ok.

> What do you mean by 'business companion files'? Are those like
> industry specific DTD companion files? Is that what you mean?
Yes, that's it.
> How do you convert from a 'business companion file' to an XCF? (if you
> can get into those details).
OK. What I below call exchange is exchange of raw data. Often raw data are not ready to use because if they were they would not be exchnage data (they need to be multi-purpose and multi-usages). The business companion files sits with the exchange data.

Before consulting this data, you need to prepare them for display. the basic thing is to apply an XSL. The advanced thing is to build index, links, full-text search and integration of different data silos. That is what we are doing with our Technology Adoc N@vigator (underlying our AirN@v product). Other candidates are for instance Jouve, enigma, .....
The conversion is therefore part of our publishing capability and this is logical as we are mastering the business rules that are needed for this. Do you think I give you enough information? If not please advise.

From Cologne meting it is clear that the XCF is not be used how the 'business companion file' is. I had a hard time to understand why (because we were the first really engaged with companion files and in the other way). But now I understgand benefits that I may have from the current works.

Regards,

Franck

> -----Message d'origine-----
> De : Benoit Bezaire [mailto:benoit@itedo.com]
> Envoyé : jeudi 6 avril 2006 15:45
> À : cgmo-webcgm@lists.oasis-open.org
> Objet : Re[2]: [cgmo-webcgm] Did we miss something?
>
>
>
> Hi Franck,
>
> I agree with you about Pandora's Box.
>
> I'm not sure I totally understand, so let me ask a few questions if I
> may.
>
> yes, the 'name' attribute will be available using the DOM, ok.
>
> What do you mean by 'business companion files'? Are those like
> industry specific DTD companion files? Is that what you mean?
>
> How do you convert from a 'business companion file' to an XCF? (if you
> can get into those details).
>
> --
>
> Regards,
>  Benoit   mailto:benoit@itedo.com
>
> This e-mail and any attachments are confidential and may be protected
> by legal privilege. If you are not the intended recipient, be aware
> that any disclosure, copying, distribution or use of this e-mail or
> any attachment is prohibited. If you have received this e-mail in
> error, please notify us immediately by returning it to the sender and
> delete this copy from your system. Thank you for your cooperation.
>
>
>
> Wednesday, April 5, 2006, 5:51:25 PM, you wrote:
>
> > Hi Ben and all,
>
> > If this file is to be used for exchange it could be that your
> > question is necessary. But if your question is dealing with the
> > viewer and the application in which he is integrated, then I think
> > there is no problem as I will get the information through the DOM.
>
> > In my mind the choice has been made clearly: for document
> > information exchange purpose of business data I will carry on with
> > my business companion files which will be the basis for
> generating my XCF.
>
> > Not sure it is a good idea to open the Pandora's Box.
>
> > Regards,
>
> > Franck.
>
> > -----Message d'origine-----
> > De : Cruikshank, David W [mailto:david.w.cruikshank@boeing.com]
> > Envoyé : mardi 4 avril 2006 22:34
> > À : Benoit Bezaire; cgmo-webcgm@lists.oasis-open.org
> > Objet : RE: [cgmo-webcgm] Did we miss something?
>
>
>
> > Ben,
>
> > I think you do have to use the bindByName call to apply an XCF via a
> > name attribute.  I don't think there is any other way to do
> it.  Are you
> > talking about addiing/modificating a name attribute via the XCF?  I
> > thought name was readonly..
>
> > Thx...Dave
>
>
> > Technical Fellow - Graphics/Digital Data Interchange
> > Boeing Commercial Airplane
> > 206.544.3560, fax 206.662.3734  <-- NEW NUMBERS
> > david.w.cruikshank@boeing.com
>
> > -----Original Message-----
> > From: Benoit Bezaire [mailto:benoit@itedo.com]
>
> > Sent: Tuesday, April 04, 2006 7:18 AM
> > To: cgmo-webcgm@lists.oasis-open.org
> > Subject: [cgmo-webcgm] Did we miss something?
>
> > Hi guys,
>
> >   I was looking into the XCF stuff lately... more precisely
> the "a la
> >   Duluc" scenario... where a user may want a companion file not for
> >   'apply' purpose, but mainly for documentation.
>
>
> >   I'm assuming a user may want the companion file in the following
> >   structure (for documentation purposes):
>
> >   <grobject id="obj1" screentip="a tip"/>
> >   <para id="obj2" screentip="another tip"/>
>
> >   I'm assuming that for the documentation case, that it doesn't make
> >   much sense to use the <bindByName> and <bindById> tags as
> is caries
> >   less information (you lose the aps type).
>
> >   So, assuming my assumptions are correct; where's the 'name'
> >   attribute in the DTD?
>
> >   It seems like I'm not allowed to do:
> >   <grobject id="obj1" name="drawing"/>
>
> >   Did we miss something?
>
> > --
>
> >  Benoit   mailto:benoit@itedo.com
>
> > This e-mail and any attachments are confidential and may be
> protected by
> > legal privilege. If you are not the intended recipient, be
> aware that
> > any disclosure, copying, distribution or use of this e-mail or any
> > attachment is prohibited. If you have received this e-mail in error,
> > please notify us immediately by returning it to the sender
> and delete
> > this copy from your system. Thank you for your cooperation.
>
>
>
>
>
> > This mail has originated outside your organization,
> > either from an external partner or the Global Internet.
> > Keep this in mind if you answer this message.
>
>
>
> > This e-mail is intended only for the above addressee. It may contain
> > privileged information. If you are not the addressee you
> must not copy,
> > distribute, disclose or use any of the information in it.
> If you have
> > received it in error please delete it and immediately
> notify the sender.
> > Security Notice: all e-mail, sent to or from this address, may be
> > accessed by someone other than the recipient, for system
> management and
> > security reasons. This access is controlled under Regulation of
> > Investigatory Powers Act 2000, Lawful Business Practises.
>
>
>
>
>
> This mail has originated outside your organization,
> either from an external partner or the Global Internet.
> Keep this in mind if you answer this message.
>


This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.