SPAM: Re: SPAM: SPAM: Re: SPAM: Re: eggs and SPAM: Re: [OPEN-ILS-DEV] IDL

Bill Erickson billserickson at gmail.com
Wed Mar 22 09:03:11 EST 2006


On 3/21/06, Mike Rylander <mrylander at gmail.com> wrote:
>
> On 3/21/06, S. K. Murphy <error23 at gmail.com> wrote:
> > Yes, thanks, that'll make discussion easier.  Now, about the
> @class_type; I
> > used that name to keep it from being confused with the <class> element;
> but
> > I have changed that.
>
> As long as it's an attribute instead of an element I'm not /too/
> concerned, but if others would like to weigh in on that...


I think the current example works well with @class.

> Another question, in the <link> element in that file, what is the @id
> > attribute?  If I understand it properly, the @field attribute has to
> match
> > one of the field's names; @table would map to my @class attribute, @key
> > would be what I had as @fkey (i changed it to @key here, too, for
> > consistency's sake).  I'm assuming @id refers to the name of the link,
> but
> > I'd just like to make sure that's correct.
>
> That's absolutely correct.  Each <link> gets a globally unique
> identifier so that the relationship can be directly addressed.  I'm
> undecided as to whether other elements deserve an @id ... my current
> feeling is that a <class>s @id should hold its name.  Anyone?



I can see either <class name=''/> or <class id=''/> working.  It makes no
difference to me...  Also, IMO, I don't see any need for forcing an @id on
every element unless it's necessary for some type of linkage.

One other comment on the example XML file.  Right now we have a couple of
objects layed out like so:

<field
 name="start_date_day"
 virtual="false"
 type="object"
 class="date">

Here, @type should be 'string' since that's how dates will be encoded.


--
Bill Erickson
PINES Systems Developer
Georgia Public Library Service
billserickson at gmail.com
http://open-ils.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20060322/4bc007e8/attachment.html


More information about the Open-ils-dev mailing list