Akara sprint in Boulder this week
Uche Ogbuji
I have some preliminary notes on agenda which I'll work up more today. Links to any notes and other putputs will also be maintained from the sprint page.:
http://wiki.xml3k.org/Akara/March_2010_Sprint
--
Uche Ogbuji http://uche.ogbuji.net
Founding Partner, Zepheira http://zepheira.com
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
TNB: http://www.thenervousbreakdown.com/author/uogbuji/
Friendfeed: http://friendfeed.com/uche
Twitter: http://twitter.com/uogbuji
http://www.google.com/profiles/uche.ogbuji
Pigneri, Rocco
Dear all,
Ticket #48 really excites me. I have a few suggestions for its overall behavior that I would like to see implemented (and that I have spent a little bit of time thinking about since I might implement it in Amara1). Since you guys are talking about this now and since I don’t see an option for me to add to the ticket, I’ll just post my thoughts here.
Here’s a list of features that I would like to see in pushbind 2.0 that I think would greatly increase its usefulness. These are in decreasing order of importance:
- It would be great if Amara automatically provided the XPath that matched the node as an attribute on all returned nodes. That’s really what has started my own investigation of into pushbind.
- Attributes should be treated equally to elements, especially for the purposes of rules. It’s a little silly (at least, as far as I can understand) that I can associate rules with elements but not attributes.
- It might be nice to add a Sax.START_ATTRIBUTE/END_ATTRIBUTE event to pushbind’s parser in order to separate the element events from the attribute events.
I could get into some detail about implementing them as well, but I’ll wait to see if there’s interest.
Thank you,
Rocco
--
You received this message because you are subscribed to the Google Groups "akara" group.
To post to this group, send email to ak...@googlegroups.com.
To unsubscribe from this group, send email to akara+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akara?hl=en.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4905 (20100301) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4906 (20100301) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4909 (20100302) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4912 (20100303) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4912 (20100303) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Uche Ogbuji
Ticket #48 really excites me. I have a few suggestions for its overall behavior that I would like to see implemented (and that I have spent a little bit of time thinking about since I might implement it in Amara1). Since you guys are talking about this now and since I don’t see an option for me to add to the ticket, I’ll just post my thoughts here.
Let's please make sure you are able to update the ticket.
Do you see the "OpenID Login" in the upper right corner? I think once you do that you can contribute without needing any further permission. Luis, can you confirm?
I'll continue the rest of the discussion on the ticket. Thanks a lot for your thoughts.
--Uche