[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cgmo-webcgm] how to add Style Properties to XCF?
I like Alt 1. In my opinion, it's easier to parse and also easier to understand... -- Benoit mailto:benoit@itedo.com Wednesday, June 15, 2005, 8:32:23 PM, Lofton wrote: LH> WebCGM TC, LH> Feedback welcome, if you have a preference... LH> I think we decided today to add Style Properties to XCF (correct?). Please LH> state your preferences about... How should we add them? LH> Alt.1: to each element in XCF, add 9 attributes with names as in the SP LH> table of 5.7.5. LH> Alt.2: to each element in XCF, add 1 attribute which is a string of 2n LH> wsp-separated simple string-valued items (names and values). LH> RECOMMENDATION: Alt.1 LH> DISCUSSION: LH> For reference, the method in 5.7.5 is setStyleProperty(name, value), where LH> name and value are type WebCGMString. Discussion and examples.... LH> Alt.2 would look like, for grobject (4.4) example: LH> ========== LH> content LH> ---- LH> <grobject apsid="myObj1" styleProperties="stroke-weight 50% LH> stroke-color #FF0000" ...> LH> DTD LH> ----- LH> <!ENTITY % grobjectEXT "" > LH> <!ENTITY % grobjectAttEXT "" > LH> <!ELEMENT grobject ( linkuri %grobjectEXT; )* > LH> <!ATTLIST grobject LH> apsid ID #REQUIRED LH> screentip CDATA #IMPLIED LH> region CDATA #IMPLIED LH> viewcontext CDATA #IMPLIED LH> visibility ( on | off | inherit) #IMPLIED LH> interactivity ( on | off | inherit) #IMPLIED LH> styleProperties CDATA #IMPLIED LH> %grobjectAttEXT; >> LH> and would contain some verbiage about the structure of the string [(name LH> wsp value wsp)+]. Such verbiage could be centralized in 4.10, "Attribute LH> encoding", and referenced from each XCF element's section. LH> Alt.1 would look like: LH> ========== LH> content LH> ----- LH> <grobject apsid="myObj1" stroke-weight="50%" stroke-color="#FF0000" ...> LH> DTD LH> ----- LH> On every element of XCF, the single styleProperty line of Alt.2 would be LH> replaced by 9 lines (if we keep text-font, 8 otherwise): LH> <!ENTITY % grobjectEXT "" > LH> <!ENTITY % grobjectAttEXT "" > LH> <!ELEMENT grobject ( linkuri %grobjectEXT; )* > LH> <!ATTLIST grobject LH> apsid ID #REQUIRED LH> screentip CDATA #IMPLIED LH> region CDATA #IMPLIED LH> viewcontext CDATA #IMPLIED LH> visibility ( on | off | inherit) #IMPLIED LH> interactivity ( on | off | inherit) #IMPLIED LH> background-color CDATA #IMPLIED LH> character-height CDATA #IMPLIED LH> fill-color CDATA #IMPLIED LH> intensity CDATA #IMPLIED LH> stroke-color CDATA #IMPLIED LH> stroke-weight CDATA #IMPLIED LH> text-color CDATA #IMPLIED LH> text-font CDATA #IMPLIED LH> raster-intensity CDATA #IMPLIED LH> %grobjectAttEXT; >> LH> and would pretty much just point to the table in 5.7.5 for contents of CDATA. LH> Alt.1 seems more natural from the usage perspective, though it is uglier LH> from the DTD-definition perspective, having to add 9 lines to every element LH> in the DTD. (That could be mitigated somewhat -- the DTD of XCF could also LH> define an entity and put it in place of the 9 lines.) LH> Preferences? LH> -Lofton.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]