W3C home > Mailing lists > Public > public-webcgm-wg@w3.org > January 2009

re[2]: [cgmo-webcgm] lineEdgeTypeDef xml coding

From: Don <dlarson@cgmlarson.com>
Date: Sat, 31 Jan 2009 17:07:06 -0600
To: Lofton Henderson <lofton@rockynet.com>, CGM Open WebCGM TC <cgmo-webcgm@lists.oasis-open.org>
cc: <public-webcgm-wg@w3.org>, Dave Cruikshank <dvdcruikshank@gmail.com>
Message-ID: <RFUxRks3UChAN1hIKCpSMjA2ODc2NQ@foghorn>

Lofton,

comments below-

 >  Don,

 >  Here is the operative DTD snippet:

 >  <!ELEMENT webcgmConfig ( fontMap?, defaultAttributes? ) >
 >  ...
 >  <!ELEMENT defaultAttributes ( lineCap | edgeCap | lineJoin | edgeJoin
 >  | lineTypeCont | edgeTypeCont | mitreLimit
 >  | restrTextType | lineEdgeTypeDef | 
 >  hatchStyleDef )+ >

 >  That means the ACI can have 0, 1, or *more* of any of the things in parens,
 >  like lineCap and lineEdgeTypeDef.  As far as I can see, there is nothing in
 >  the ACI chapter to further restrict.

 >  I think that is okay.  If we have a rule like "last one wins", then that 
 >  would tell a viewer what to do with multiple occurrences of lineCap in the 
 >  ACI file.  For lineEdgeTypeDef, it would only be multiple occurrences if it
 >  were defining the same line type index, in which case again, "last one
 >  wins".

 >  Does anyone see a problem with that?

 >  If it's okay, then we can disambiguate with a single sentence (or two) in 
 >  the chapter.

That should suffice.
  
I will also try to use multiple lineEdgeTypeDef in one of my ACI tests.

Did you see my question at end of my last email regarding negative lineIndex?

  [ Another question related to lineEdgeTypeDef, is a negative lineIndex valid
  in ACI lineEdgeTypeDef?  I re-call that we debated wheter or not we wanted
  to do this is our last f2f, but just wanted to make sure. As the spec is
  now, negative lineIndex is NOT valid.]

Don.
 >  -Lofton.

 >  At 03:26 PM 1/31/2009 -0600, Don wrote:
 >  >All
 >  >
 >  >The spec is not clear to me that an ACI file can contain multiple
 >  >lineEdgeTypeDef elements and attribute sets.
 >  >
 >  >For example is this valid?
 >  >
 >  ><webcgmConfig
 >  >   <defaultAttributes>
 >  >     <lineEdgeTypeDef lineIndex="1" repeatLength="100" dashLength="10 2 5 
 >  > 2" />
 >  >     <lineEdgeTypeDef lineIndex="2" repeatLength="100" dashLength="10 2 
 >  > 10,2" />
 >  >     <lineEdgeTypeDef lineIndex="3" repeatLength="100" dashLength="10 2 5 
 >  > 2 5 2" />
 >  >   </defaultAttributes>
 >  ></webcgmConfig>
 >  >
 >  >
 >  >Since a Metafile has only 1 lineCap attribute by definition, an ACI can
 >  >have only 1 lineCap element but since there can be multiple lineEdgeType
 >  >definitions in a Metafile, I would think that specifying multiples is
 >  needed.
 >  >
 >  >
 >  >Another question related to lineEdgeTypeDef, is a negative lineIndex valid
 >  >in ACI lineEdgeTypeDef?  I re-call that we debated wheter or not we wanted
 >  >to do this is our last f2f, but just wanted to make sure. As the spec is
 >  now,
 >  >negative lineIndex is NOT valid.
 >  >
 >  >
 >  >Don.
 >  >
 >  >---------------------------------------------------------------------
 >  >To unsubscribe from this mail list, you must leave the OASIS TC that
 >  >generates this mail.  Follow this link to all your TCs in OASIS at:
 >  >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


 >  ---------------------------------------------------------------------
 >  To unsubscribe from this mail list, you must leave the OASIS TC that
 >  generates this mail.  Follow this link to all your TCs in OASIS at:
 >  https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
Received on Saturday, 31 January 2009 23:09:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 31 January 2009 23:09:58 GMT