RE: BPSS identifiers needed

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

The namespace identifiers follow ebXML Messaging and CPPA identifiers 

http://www.oasis-open.org/committees/ebxml-bp/schema

by using the OASIS TC name followed by schema.

I just used local file names for the final part of the path.

The TC should decide what names to use in the final part of the path,
such as, bpss-2_0.xsd or bpss-signal-2_0.xsd.

Dale



-----Original Message-----
From: Monica J. Martin [mailto:Monica.Martin@Sun.COM] 
Sent: Tuesday, December 14, 2004 4:46 AM
To: Dale Moberg
Cc: BPSS ebXML
Subject: Re: BPSS identifiers needed

mm1: Dale these all look good although I have one question if schema is 
ebbpss or ebbp for the namespace URIs?

> A URI for the namespace of the schema (targetNamespace value)
>
>http://www.oasis-open.org/committees/ebxml-bp/schema/ebbpss-2_0.xsd
>
>  .....
> [We would also ask to have this URL resolve to the most current ebBP 
> schema as well as use the URL for the core schema as a schemaLocation 
> value. For the namespace, we follow the pattern of Messaging and CPPA.

> The TAB does not seem to prescribe namespace values, probably wisely.]
>
> .......A namespace URI for the signal schema
>
>
http://www.oasis-open.org/committees/ebxml-bp/schema/ebbpss-signal-2_0.x
sd.....
>
Thanks.