Ted Leung wrote:
- There are other nasty issues around putting custom attribute
name/ value pairs in the label field: what about conflicts with
OOTB attributes, what happens when stamping a new kind creates a
conflict, how do we validate input in this field, how do we parse
and report errors on complex values on non-text OOTB attributes
(and what if they contain commas, like dates eg "Feb 24, 2006",
which are illegal in the label field)? What about OOTB attributes
that are references (emailAddress lists, etc)?
This one is definitely on my list.
Andi said the other day "I have an idea about how to do custom
attributes".. Andi do you want to chime in?
One thought I had personally is that schema.Annotation is one way to
make a 'namespace' on attributes. I think it isn't necessarily important
that no attributes ever conflict, but it is important that no
user-defined attributes conflict with existing item-level attributes. So
to me, that says that we just need a way to segregate the user-level
attributes from the normal attributes.
Alec
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
