OASIS ebXML Core (ebCore) TC

  • 1.  Meeting on Friday, Jan 8th?

    Posted 01-06-2010 23:12 
    Do we have agenda items for our scheduled meeting for ebCORE on Jan 8th at 11:00 am Pacific Time? If not, our next regularly scheduled ebCORE meeting would be Jan. 22nd. Please let me know if you would like to meet this Friday, or cancel.

I will be out of country visiting my son and daughter-in-law, and our brand new grandson in Uganda Jan. 9th- Feb 1st. Josiah Michael was born Dec. 19th at 7 lbs 1 oz, and 19.5 inches long. Mom and baby are doing well, and Grandma can't wait to hold him! :-)

I will not have access to email during that time. I have set up the telecon for ebCORE use on Friday Jan. 22nd, so please go ahead without me if you have agenda items and quorum.

Kathryn


Kathryn Breininger
Manager, Document Authoring & Release
Product Standards Office
Boeing Research & Technology
The Boeing Company

MC 62-LC
425-965-0242 desk
425-512-4281 cell
425-237-4582 fax


  • 2.  RE: [ebcore] Meeting on Friday, Jan 8th?

    Posted 01-07-2010 10:56 
    Hello,

I have a topic, but there is no rush so it could wait until
a later meeting. 

An idea I would like to discuss relates to last year's
discussion on PartyId:
http://lists.ebxml.org/archives/ebxml-dev/200908/
http://lists.oasis-open.org/archives/ebcore/200908/threads.h
tml

Could we extract the section on PartyId from the CPA 3.0
draft and publish it as a separate, very small,
specification?
The CPA editors would need to agree to it obviously.

Reasons:
- There is a real need among users for something like this.
- If we wait for CPA 3.0 to finish it may be many months,
and it would be buried in a spec that some potential users
will never look into.
- It would be a nice, low-effort deliverable for this TC.

If people agree, I volunteer to do the necessary editing
(mostly cutting and pasting) and formating but the effort is
minimal. 

The proposal would be to be a bit more general and define
three URNs instead of one.

1) urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523

As described in the PartyId section on CPA 3.0.  When we
post the ICD list on the Wiki, we would have a useful
resource to promote its use

Examples:

urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523:0060 is
DUNS
urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523:0088 is
GS1 GLN

Question is whether we keep the "ebxml-cppa" or change to
"ebcore"? Is this better:

urn:oasis:names:tc:ebcore:partyid-type:iso6523:0060

2) urn:oasis:names:tc:ebxml-cppa:partyid-type:iso15022

A similar system. It was mentioned by Charles Kilkenny on
the mailing list. Field 95R of ISO 15022 defines a similar
meta-schema, used in financial services. Four character code
identifiers, see
http://www.iso15022.org/Data_Source_Schemes.pdf for an
overview

Examples:

urn:oasis:names:tc:ebxml-cppa:partyid-type:iso15022:XETR is
"Deutsche Boerse AG: XETRA"
urn:oasis:names:tc:ebxml-cppa:partyid-type:iso15022:XLON is
"London Stock Exchange"

3) urn:oasis:names:tc:ebxml-cppa:partyid-type:unregistered

A standardized prefixes for arbitrary unregistered,
bilaterally agreed code systems.  
Of use for people want to use an official IANA-registered
URN but have an unregistered classification scheme.

Examples:

urn:oasis:names:tc:ebxml-cppa:partyid-type:unregistered:myho
megrownpartyidscheme

Unrelated to the above, I posted an ebBP question, but we
can also discuss that during next week ebCore-CPA
SubCommittee meeting.

Pim


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 3.  RE: [ebcore] Meeting on Friday, Jan 8th?

    Posted 01-08-2010 18:05 
    I haven't heard from anyone else... I assume that means folks are not online or available?   


Kathryn Breininger


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 4.  Party Id proposal

    Posted 02-15-2010 13:40 
     
Hello,

I got some feedback from potential users confirming my the
interest in pursuing the idea of a "mini spec" on PartyId
type.

So I took the relevant paragraphs of the CPA draft (which is
focussed on one mechanism, based on ISO 9635, based on
requirements from ebXML users in Japan some years ago),
reworked and extended it with some other meta-classification
schemes, and added some (non-normative) discussion of sample
applications that could use a standard URN-based PartyId
type, including CPA, ebMS, UBL, SBDH (plus CEFACT XML and
OAGIS).

Please let me know what you think.

If we have a call on Friday, we can discuss it.

Pim


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 5.  Re: [ebcore] Party Id proposal

    Posted 03-05-2010 16:52 
    



I think it’s useful to have an uniform notation for identifying the namespace / naming scheme for the Party id. So I support this spec. I however don’t know if this can be a specification, because we’ll then need to write a conformance section and I was wondering what our conformance target(s) would be.

    
Some remarks on the draft:

    

    • Note that according to RFC3121 which defines the oasis URN namespace, names in this namespace should be used for identifying OASIS related documents. The names constructed according to this specification do not identify OASIS documents. So the oasis URN namespace wouldn’t be right. I don’t know if this might be an issue or not. This notation is already used in CPPA v2, so if no comments were made on that spec, I would expect this to be allowed.

    • The goal / scope of this specification as described in the Introduction section migth be confusing as it might seem that this spec defines a formal URN namespace. The intention however is to specify uniform URN’s for identifying naming schemes. 

    • The construction of an URN differs for ISO6523 and the other described catalogs. I would propose to use one scheme like: urn:oasis:tc:ebcore:partyid-type:<catalog-identifier>:<scheme-id within catalog>. Assuming that every naming schme registered in ISO6523 has an ICD the URN for a naming scheme would be urn:oasis:tc:ebcore:iso6523:<icd>. The URN for the ISO6523 would then be urn:oasis:tc:ebcore:iso6523:0060
      


    
Regards,
    
Sander   

    
 

    
 
    
 
    
 


    
On 15/02/2010 14:40, "Pim Eijk, van der" <pvde@sonnenglanz.net> wrote:

    


    
Hello,

    
I got some feedback from potential users confirming my the
    
interest in pursuing the idea of a "mini spec" on PartyId
    
type.

    
So I took the relevant paragraphs of the CPA draft (which is
    
focussed on one mechanism, based on ISO 9635, based on
    
requirements from ebXML users in Japan some years ago),
    
reworked and extended it with some other meta-classification
    
schemes, and added some (non-normative) discussion of sample
    
applications that could use a standard URN-based PartyId
    
type, including CPA, ebMS, UBL, SBDH (plus CEFACT XML and
    
OAGIS).

    
Please let me know what you think.

    
If we have a call on Friday, we can discuss it.

    
Pim

    

    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


Related Content