[Osr-101] Client side XSLT parameters

[Andreas Wuest]

Hi

On 13.7.2007 12:31 Uhr, Michael Wechner wrote:

> Andreas Wuest wrote:
> 
>> Hi
>>
>> On 11.7.2007 16:03 Uhr, Michael Wechner wrote:
>>
>>> Hi
>>>
>>> At the Lenya hackathon Thomas suggested to introduce client side XSLT 
>>> parameters as by enhancing the introspection as follows:
>>>
>>> <introspection>
>>> <resource>
>>>  <edit>
>>>    <style href="/foo/bar.xsl">
>>>       <parameter name="" value=""/>
>>>       ...
>>>
>>>
>>> I think that would make a lot of sense.
>>
>>
>> I agree.
> 
> btw, I have added an amendment
> 
> http://neutron.wyona.org/amendments/xslt-parameters.html

Looks ok to me.

Ah, and finally, the "<" and ">" show correctly! :)

>> From a protocol perspective we have to be a bit cautious though. First 
>> of all, we have this <style> element. Is this XSL only, or do we want 
>> to use this for different things (e.g. CSS, etc.)?
> 
> good question, so far I think we only considered XSLT, but I guess CSS 
> would also make sense.
> 
> What did we implement in the case of Yulup? I guess only XSLT?

XSLT only, yes. I think Andreas Hartmann once requested a feature like this.

>> If we exlusively want to use it for XSL, then I'm fine with the above. 
>> If we also want to use it for CSS, etc., then parameters might not 
>> make sense for certain styles.
> 
> well, we could add a mime-type attribute, e.g
> 
> <style mime-type="text/css" href="/foo/bar.css"/>
> 
> <style mime-type="application/xhtml+xml" href="/foo/bar.xsl">
>  <parameter name="....
> 
>>
>> But maybe we should simply introduce a @type attribute for the style, 
>> which tells us what kind of style it is. If there are parameters for a 
>> CSS style, then it is simply ignored by the client.
> 
> you mean like I describe above?

Yes, exactly! I'm fine with that.

-- 
Kind regards,
Andi