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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

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


Subject: Re: [office-metadata] grouping use cases


Bruce,

Tags would work. Perhaps a litely constructed set of categories or pots 
into which the use cases can be sorted? That sort of thing?

In other words, they might have the titles they do now, for instance, 
followed by: (enhanced content), etc.

Hope you are having a great day!

Patrick

Bruce D'Arcus wrote:

>
> On Jul 20, 2006, at 11:31 AM, Patrick Durusau wrote:
>
>> Note I am not disagreeing with your approach but merely cautioning 
>> that we need to remember that a use cases document is not simply 
>> technical input into a process but a political document to get buyin 
>> from users who may not be at ease with spotting the similarities 
>> between their needs and the needs of others.
>
>
> Yeah, I'm not really thinking we should physically partition the 
> document in this way, because it would be artificial.
>
> But maybe just have a statement at the beginning, and perhaps, um, 
> tags? I think that would help the TC better understand the document 
> when we present it to them.
>
> Bruce
>
>
>
>

-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

Topic Maps: Human, not artificial, intelligence at work! 




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