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

Re: [cgmo-webcgm] lineEdgeTypeDef xml coding

From: Lofton Henderson <lofton@rockynet.com>
Date: Sat, 31 Jan 2009 15:55:20 -0700
Message-Id: <>
To: Don <dlarson@cgmlarson.com>, CGM Open WebCGM TC <cgmo-webcgm@lists.oasis-open.org>
Cc: public-webcgm-wg@w3.org>,Dave Cruikshank <dvdcruikshank@gmail.com>


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.


At 03:26 PM 1/31/2009 -0600, Don wrote:
>The spec is not clear to me that an ACI file can contain multiple
>lineEdgeTypeDef elements and attribute sets.
>For example is this valid?
>   <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>
>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.
>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:
Received on Saturday, 31 January 2009 22:56:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:23:41 UTC