OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-cc-review message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [regrep-cc-review] Kickoff!

> It would be good if someone can take a defense of 
> (b) and see 
> if our arguments for (a) have holes in them.

I have some points to be solved still. Not in favour of
(b) but possible obstacles for (a)

- DictionaryEntryName is composed of parts. Shall the parts
be stored in the ExtrinsicObject, they probably will not be
interanionalized. Not sure if they would need to anyway,
but modellers here defined them in Finnish, not English.

- A RIM Slot can have n values, but each value has a maximum
length. I've tweaked JAXR provider to keep values order, and
it works in my case, but that is not according to standard.
(Any plans to get RIM Slot values as an ordered collection?)

- By keeping Slots' values order I'm able to store longer
texts to a slot and, based on slot.type decide wether to
handle it as many 'short' strings (1 per value), a 'long'
string (catenate all) or as many 'long' strings (catenate
all and tokinize).

- 0..* and 1..* properties are harder to handle if the
possible values are not known beforehand. How to name the
slot then??


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]