Re: Pending vocabulary issues

From: Emmanuel Pietriga <>
Date: Wed, 11 May 2005 09:20:11 +0200

Ryan Lee wrote:
> Quite apart from the intermediate tree issue, I am eager to reach some
> closure on the following vocabulary terms for implementation:
> 1. one term for turning a URI into a URL in presentation
> 2. set of 'transform' terms, separated from styling
> 3. class hook
> 4. primaryClasses
> For 1., I agree that behavior is a separate issue, but turning a URI
> into a URL is a common enough occurence that it's worth including in
> core. I am going to include it since I think we've all pretty much
> stated our agreement and consider the matter resolved.

Yes. Wouldn't there be some XLink term we could reuse here? (just

> For 2., I ultimately proposed what's in:
> Agreeing on a name for this set of terms is also an important task. I
> don't much care what that name is.

You mean "PropertyTransform"?

> For 3., we come back a bit to the intermediate tree. If we are going to
> have a class attribute on tree elements, then we need a way to assign a
> value to that class in core. Back to hooks - I propose fresnel:hook
> "foo"^^xsd:string on a lens.

"hook" seems a little bit too general for me. Could we introduce the
notion of styling in it? Maybe "stylingHook", or "classHook".

> 4. I've already added primaryClasses to the core vocab but I don't
> recall hearing agreement that it's the right thing to do from all.

What was it about? I don't remember this.

Emmanuel Pietriga
INRIA Futurs - Projet In Situ    tel : +33 1 69 15 34 66
Bat 490, Universit Paris-Sud    fax : +33 1 69 15 65 86
91405 ORSAY Cedex  
Received on Wed May 11 2005 - 07:20:54 EDT

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:40:51 EDT