[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-comment] wsrp markup
In general, consumers are not required to supply any non-default CSS classes so to Timo's question - you can just plug a WSRP service in without defining a CSS file; it's up to the Consumer to provide an optimized/customized/vendor-or-implementation-specific CSS file. -----Original Message----- From: Rich Thompson [mailto:richt2@us.ibm.com] Sent: Wednesday, October 09, 2002 8:21 AM To: 'wsrp-comment@lists.oasis-open.org' Subject: Re: [wsrp-comment] wsrp markup The specification defines class names, but it would be up to Consumers to publish a css file that mapped those class names to style definitions. I think we could publish a css file that contained just empty definitions, but don't see much value to doing so. Timo Tetzlaf <Timo.Tetzlaf@met To: "'wsrp-comment@lists.oasis-open.org'" ris.de> <wsrp-comment@lists.oasis-open.org> cc: 10/09/2002 05:01 Subject: [wsrp-comment] wsrp markup AM > is there already an available css file (alpha, beta or similar) for > the wsrp markup, Style and Rewriting Spec. 1.2 ? > Timo > ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC