RE: [election-services] Better data model - simple item - "Id"

We used to have an IDtype attribute, but changed this to recommend
use of an xsi:type instead so the value could be validated. Some people don’t
like xsi:type (although nobody on this committee objected to it, either at the
time or later), so we could allow either.

 

Paul

 

 

From: David RR Webber (XML)
[mailto:] 

Sent: 20 April 2009 18:52

To: Paul Spencer

Cc: 'eml '

Subject: RE: [election-services] Better data model - simple item -
"Id"

 

Paul,

 

I was grasping for a general term - perhaps - PhysicalID with an
optional IDtype attribute (seeing it is an element).

 

Thanks, DW

-------- Original Message
--------

Subject: RE: [election-services] Better data model - simple item -
"Id"

From: "Paul Spencer" <>

Date: Sun, April 19, 2009 11:50 pm

To: "'David RR Webber (XML)'" <>

Cc: "'eml '" <>

I wouldn’t use NumberId as there is no guarantee that this ID will
be numeric.

 

Paul

 

From: David RR Webber (XML) [mailto:] 

Sent: 20 April 2009 00:05

To: Paul Spencer

Cc: 'eml '

Subject: RE: [election-services]
Better data model - simple item - "Id"

 

Paul,

 

That is helpful feedback.  I'll revisit on the use analysis.
 So perhaps better would be to have NumberId as the element and RefId for
the internal one.  Clearly when an attribute its being used to indicate
linkage between content such as polling place description and geo map data, and
so on.

 

Thanks, DW

-------- Original Message --------

Subject: RE: [election-services] Better data model - simple item -
"Id"

From: "Paul Spencer" <>

Date: Sun, April 19, 2009 12:25 am

To: "'David RR Webber (XML)'" <>, "'eml
'"

<>

Hi David,

 

The original intention was that Id exists as an element when it is
an external Id such as an electoral roll number. It is used as an attribute
when it is an internal system Id.

 

Paul

 

From: David RR Webber (XML) [mailto:] 

Sent: 18 April 2009 23:36

To: eml 

Subject: [election-services] Better
data model - simple item - "Id"

 

Team,

 

This might be an easy one to fix?  We appear to use
"Id" as an attribute everywhere - but we have 4 different definitions
for it.

 

In emlcore we could add a single type definition - and then
reference that everywhere "Id" occurs.

 

A small step for EML...

 

Are there one or two other candidates?  I don't want to have
too many of these to do at this point - but obvious ones that are highly used
seem like worthwhile to fix at this point.

 

Thanks, DW

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

______________________________________________________________________

This email has been scanned by the MessageLabs Email Security System.

For more information please visit http://www.messagelabs.com/email 

______________________________________________________________________

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

______________________________________________________________________

This email has been scanned by the MessageLabs Email Security System.

For more information please visit http://www.messagelabs.com/email 

______________________________________________________________________

______________________________________________________________________

This email has been scanned by the MessageLabs Email Security System.

For more information please visit http://www.messagelabs.com/email 

______________________________________________________________________