[Versa] Issue 100A proposal, extension functions

[Uche Ogbuji]

On Sun, 2005-09-04 at 06:40 -0400, Chimezie Ogbuji wrote:
> Attached is the same spec draft with section 7.7 added:
> 
> 7.7. Function Names and Extensions
> 
> 7.7.1. Function Name Expansion
> 
> All function names are Qnames as given by 'Namespaces in XML.'   
> Qnames are all expanded the same way by the implementation.  
> References to unbound namespace prefixes should always raise the same
> error (for variables, node queries, and function names) indicating to
> the user that the prefix used is unbound.
> 
> The following namespaces prefix to URI bindings should be registered by default:
> 
> rdfs    http://www.w3.org/2000/01/rdf-schema#
> rdf     http://www.w3.org/1999/02/22-rdf-syntax-ns#
> dc      http://purl.org/dc/elements/1.1/
> xs      http://www.w3.org/2001/XMLSchema#
> owl    http://www.w3.org/2002/07/owl#
> vtrav  http://rdfinference.org/versa/0/2/traverse/ 
> versa http://rdfinference.org/versa/0/2/ 

I think we should eliminate vtrav and all other derived Versa
namespaces, and just use the main Versa namespace.

Also, are we committed to the namespace as the primary vehicle for Versa
versioning?  This can be a sticky choice, but then again, all of them
can be.

And remember that we now have rdfversa.org, and see my earlier namespace
suggestion.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html