[Dev] Proposal: simplify parcel XML namespaces

[Lisa Dusseault]

XML namespaces are frequently set to HTTP URLs even though they might  
well be unreachable.  The use of a domain-name plus path is to help  
ensure uniqueness (because we own the domain name) and the HTTP in  
front is just to make it a valid scheme.

Which reminds me, "parcel:" is not a valid scheme -- some XML parsers  
are going to choke on that.  (I know that because they choke on the  
"DAV:" namespace).

Also, Phillip, what is that going to mean for the use of prefixes in  
parcel XML?

lisa

On Jun 24, 2005, at 5:18 PM, Brendan O'Connor wrote:

> I should add: when I was learning parcel xml, I tried to fetch those  
> url's in a browser, and found it a bit confusing until I concluded  
> they must be there only for universal naming purposes (like java  
> packages' reverse-dns convention).
>
> if unique naming across 3rd parties is the URIs' main design goal, a  
> system using dns would be good, esp. if the uri's were http:// links  
> that gave useful information
>
> but (python paths == repository paths == namespace URI's) is awfully  
> convenient..
>
> brendan
>
>
>
> On Fri, 24 Jun 2005 17:03:17 -0700, Brendan O'Connor  
> <brenocon at gmail.com> wrote:
>
>> was the http:// syntax ever intended to get an actual document off  
>> the web?  [they don't work now at least]
>>
>> On Fri, 24 Jun 2005 17:02:22 -0700, Phillip J. Eby  
>> <pje at telecommunity.com> wrote:
>>
>>> Now that all Chandler parcels are using the schema API, we have the  
>>> option of getting rid of the messy 'http:' URIs for defining parcel  
>>> namespaces.  I'd like to propose that we move to a "parcel:" URI  
>>> scheme, of the form "parcel:osaf.framework.blocks"  This would let  
>>> us use the same names in parcel.xml as we would use in Python code,  
>>> making the namespaces easier for humans to read, write, and  
>>> remember.
>>>
>>> Basically, we would go from this:
>>>
>>>     <core:Parcel xmlns:core="http://osafoundation.org/parcels/core"
>>>           
>>> xmlns="http://osafoundation.org/parcels/osaf/framework/blocks"
>>>           
>>> xmlns:main="http://osafoundation.org/parcels/osaf/views/main"
>>>           
>>> xmlns:detail="http://osafoundation.org/parcels/osaf/framework/ 
>>> blocks/detail"
>>>           
>>> xmlns:amazon="http://osafoundation.org/parcels/osaf/examples/amazon"
>>>           
>>> xmlns:doc="http://osafoundation.org/parcels/osaf/examples/amazon">
>>>
>>> To this:
>>>
>>>     <core:Parcel
>>>          xmlns:core="parcel:core"
>>>          xmlns="parcel:osaf.framework.blocks"
>>>          xmlns:main="parcel:osaf.views.main"
>>>          xmlns:detail="parcel:osaf.framework.blocks.detail"
>>>          xmlns:amazon="parcel:osaf.examples.amazon"
>>>          xmlns:doc="parcel:osaf.examples.amazon">
>>>
>>> Any thoughts?
>>>
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>>
>>> Open Source Applications Foundation "Dev" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/dev
>>
>>
>>
>
>
>
> -- 
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>