[rights-specification] CR00002

[Krishna Sankar <ksankar@cisco.com>]

Hi,

	Here is Eve Maler's excellent summary (as usual). 

Tom/Hari, can you invite Eve for our next spec con call ? The only
problem could be that, next spec call succeeds the general body call and
so we might not be able to fix a time. But a con call discussion with
Eve would be the next POA on CR000000002.

cheers

-----Original Message-----
From: Eve L. Maler [mailto:eve.maler@sun.com] 
Sent: Thursday, August 29, 2002 8:20 AM
To: Krishna Sankar
Subject: Re: Hi


Hi Krishna,

Nice to hear from you!  I'll try to answer your questions/issues very 
briefly here, but it might be easiest to join your telecon and do a 
better job of it interactively.  (I assume you mean Wednesday September 
4 at 2pm PT/5pm ET?  I can be free then.)  A few notes below:

Krishna Sankar wrote:
> Eve,
> 
> 	Long time no see. Heard that you did a good job with the forum
> panel.
> 
> 	Anyway, we, in the Rights Language TC have a change request
> which I think you could solve ! We read thru your UBL Code List rules
> specification.
> 
> 	Let me start at the beginning. We have a Change Request from
> MPEG on country codes (attached) which occasionally change and
sometimes
> the codes are reused :o( So we are exploring schemes that capture some
> related metadata to make the country code unique. We are looking at
ISO
> and the UBL Code List specification.
> 
> 	Have a few questions on the UBL :
> 
> 	What does an Agency stand for ? From what I know, it would be
> things line UNSPC for prod codes. I assume the utility of an agency is
> when there are multiple organizations defining things in a domain.

Typically in real deployments, the agency ID is a code, which itself 
should theoretically need its own second-order code metadata to be 
uniquely identified.  We haven't solved this yet because the easiest way

would be to get the ebXML Core Components folks to recognize this.

> 	In the XrML domain, version is not possible but a date could be
> used. Do you see a use for it in the general specs ?

If you're using an ISO code list, it does have a version.  A date could 
also serve as the version for the whole code list.  From the document 
you forwarded, it appears the date is desired for individual codes, 
which I'm not familiar with.  From my understanding, 
backwards-incompatible changes in real (commercially managed) code lists

are extremely rare, so I'm not sure what's going on here.  I think I 
need to know more, but in short, our recommendations don't prevent 
anyone from adding *more* metadata if they wish -- but the version is 
required.

> 	Is there a schema ? Or is the UBL Code List document a
> recommendation/best practice ?

The document is a recommendation for how to *create* schemas for code 
lists used in a certain fashion, so in a sense it's a meta-schema.  It's

normative for any UBL-native code lists, but merely a recommended best 
practice for others.  If XrML uses a particular official code list, for 
example, ideally you'd want to simply import the code list schema module

that the owner (ISO or UN/ECE or UCC or whoever) created.

> 	Do you have a namespace for this ?

Each code list module would have its own namespace.

> 	If we want to use this, do you expect us to extend it ? For
> example chuck the version and add a date element.

If you're following the recommendations and want to achieve true 
semantic clarity according to the ebXML Core Components ontology, you 
need version.  But you could add date.

> 	I had suggested to the group to see if you would be available
> for a con call Wed 2:00 PST. I think we could use your information
> modeling skills and get some direction on this. (You are welcome to
> attend our f2f in Cisco September 11,12,13!)

Sorry, can't attend the F2F!  But could join the call if I'm right about

the date.

Best,

	Eve

-- 
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 883 5917
XML Web Services / Industry Initiatives      eve.maler @ sun.com