Scott, That's a valid question. Here's the counter-argument.
The motive for allowing formatting in titles comes from several sources: 1. In Requirements, formatting often has significance, i.e. an organization may have standards for formatting words with colors or styles (maybe RED for critical). 2. In scientific and engineering domains, linear text is often not adequate. Some terms have superscripts or subscripts. 3. National language may need to be indicated. This can be done using the xml:lang attribute. The dc:title property will be used in many ways, so we shouldn't take a least common denominator approach. Web pages can certainly display the formatting in tables, paragraphs, headings, etc.. When the title needs to be put in a plain text widget, then the formatting can be removed, i.e. just take the text content (which is what most text indexers would do). Even if we restricted dc:title to plain text, putting it in widgets might require making some modifications to it, e.g. if the content is very long we'd have to truncate or abbreviate it. That wouldn't cause us to impose a length limit. (would it?) Given that rich text has utility, and that turning rich text into plain text is fairly easy, I think we should allow valid XHTML <span> content in dc:title. Regards, ___________________________________________________________________________ Arthur Ryman, PhD, DE Chief Architect, Project and Portfolio Management IBM Software, Rational Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063 Twitter | Facebook | YouTube From: Scott Bosworth <[email protected]> To: [email protected] Date: 04/08/2010 09:18 AM Subject: Re: [oslc-core] rich text fields Sent by: [email protected] At the risk of unsettling the consensus here, I still have to wonder why we are suggesting that dc:title be rich text rather than just plain text ? (rich text for dc:description makes total sense to me). To Jim C's point on the workgroup call yesterday, if we consider how tools will want to use this data, the typical use cases probably include showing the titles of resources in lists, tables, drop-downs, etc. Titles in this context would seem to have arbitrary fonts, colors, emphasis, etc or the burden would be put on the client to strip out the markup. Since this is likely one of the most commonly used properties in our integration scenarios, if we want it to be rich text, it would be useful to confirm that's the desire of the domain workgroups and the most common thing for tools to share the data in this form, otherwise, I would recommend we just make things as simple as possible for clients and call the oslc dc:title property plain text. Sorry to nitpick...Scott Scott Bosworth | IBM Rational CTO Team | [email protected] | 919.486.2197(w) | 919.244.3387(m) | 919.254.5271(f) Dave ---04/07/2010 02:17:21 PM---Got it. Thanks Arthur. - Dave From: Dave <[email protected]> To: [email protected] Date: 04/07/2010 02:17 PM Subject: Re: [oslc-core] rich text fields Got it. Thanks Arthur. - Dave On Wed, Apr 7, 2010 at 1:38 PM, Arthur Ryman <[email protected]> wrote: > Dave, > > We also discussed limiting the content of dc:title and dc:description as > follows: > > 1. The value of the dc:title property should be a single line of text, so > it should be restricted to be valid content of a <span> element. > 2. The value of the dc:description property may be multiple lines of text, > so it should be restricted to be valid content of a <div> element. _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
