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] Re: Length vs. order of Slot values [was: Current Slot Issues]


> <Joe>
> The following is a summary of our current Slot issues - please provide
> feedback.
> </Joe>
> 
> Here is my feedback re: first two aspects (also, see
> http://www.oasis-open.org/archives/regrep/200306/msg00051.html):
> 
> <Joe>
> (1) Maximum length - a restrictive feature
> 
> Slot attribute "values" is of Data Type "Collection of LongName" (128
> characters)
> 
> QUESTION: Should the length be increased to (for example) 256
> characters? This may be non-issue if slot values are ordered (see
> below), as they can be "chained together".
> 
> (2) Order of Slot values
> 
> Slot attribute "values" should be changed from Data Type 
> "Collection of
> LongName" to Data Type "Ordered Collection of LongName".
> </Joe>
> 
> I suggest that we don't restrict the length of Slot values. 
> This would make
> ordering, as a solution of chunking long values, unnecessary. 
> I'd like to
> consider the same approach for other attributes, like
> RegistryObject.description, ...
>
> Nikola

+1 for no max length. I didn't push chunking forward cause this seems
to be the neat way to do it.

Regarding order, not crazy about this argument but brainstorming:
- order could indicate preference, importance, timeline sequence, etc.
- order can be ignored if not required.

Diego


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