Well, I think including semantic markup within templates is a bad idea for two reasons: first, because it won't work, as you've noticed already. Second, I'm just against adding semantic markup directly to pages on principle: I think it should always be done through templates, and only templates should contain actual semantic tags. I'm aware that I'm in the minority on this one, but I think it's an important abstraction that prevents users from having to learn semantic markup language, or the specific relation/attribute names that should be used, and allows you to change relation/attribute names at any point.
I don't think having many fields is necessarily a bad thing. Think of those Wikipedia infoboxes that contain dozens of fields. You can always add code to the template to only display fields if they're not empty; a lot of Wikipedia infoboxes have those too. And if an existing template doesn't handle some specific of data that someone thinks it should, they can just add another field to that template, then use that field. -Yaron On 7/24/07, Uschold, Michael F <[EMAIL PROTECTED]> wrote: > See inline comments. > > > ========================== > Michael Uschold > M&CT, Phantom Works > 425 373-2845 > [EMAIL PROTECTED] > ========================== > > ---------------------------------------------------- > COOL TIP: to skip the phone menu tree and get a human on the phone, go > to: http://gethuman.com/tips.html > > > > -----Original Message----- > From: Yaron Koren [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 18, 2007 1:49 PM > To: Uschold, Michael F > Cc: [EMAIL PROTECTED]; > [email protected]; Kitzmiller, Ted; Folger, Deborah > H > Subject: Re: [Semediawiki-user] Markup within a text field > > I would say including semantic markup within the values of a template is > a bad way to go. > > MICHAEL: how do you measure goodness/badness? What bad things happen > that offset the benefits I wish to experience? > -- > > Thankfully, it's not needed. If you want to store additional semantic > data, such as related project(s), you should just create a field or > fields for that data. > > MICHAEL: this will work only if you know beforehand exactly what kinds > of semantic information you might have in the text field. In that case, > your proposal will work with the proviso that there could become too > many fields cluttering up the template. However, I'm interested in the > general case where it cannot be known beforehand what kind of > information will go into the text field. So the extra fields approach > will not work in that case. > -- > > For project pages where you don't want to include a specific piece of > semantic data, you can just leave out that field from the template. > > MICHAEL: then you somehow need to have a way to tell when a field should > show up and when not. This adds a layer of complexity, but could be > useful. > > -Yaron > > On 7/18/07, Uschold, Michael F <[EMAIL PROTECTED]> wrote: > > > > > > Suppose you want to have a semantic template, for entering information > > > such as a project proposal. > > You want some outer level fields like: > > * Title > > * Author > > * Objectives > > * Summary > > * Description > > > > etc. > > > > Some of these (e.g. Summary and Description) are text fields (i.e. > > datatyp properties with string as range. One would like to ALSO mark > > > up the content in these fields semantically. > > For example, in the Summary field, one might be asserting that another > > > project is closelyRelated to the project being proposed. > > > > In principle, this would mean nested markup within a text field, which > > > I presume is not allowed. > > > > If one wants to have the markup of the detailed text itself, then one > > may have to give up the outer level template fields as being rdf > > properties, and instead just have a text header indicating them. > > > > This means you cannot ask a question like: "I want to know about all > > projects whose Project Summary field mentions another project" > > > > Has anyone else encountered this? > > Does anyone have any good ideas about how to navigate the tradeoffs > > and do something useful? > > > > Michael > > > > > > > > ========================== > > Michael Uschold > > M&CT, Phantom Works > > 425 373-2845 > > [EMAIL PROTECTED] > > ========================== > > > > ---------------------------------------------------- > > COOL TIP: to skip the phone menu tree and get a human on the phone, go > to: > > http://gethuman.com/tips.html > > > > > > ---------------------------------------------------------------------- > > --- This SF.net email is sponsored by DB2 Express Download DB2 Express > > > C - the FREE version of DB2 express and take control of your XML. No > > limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Semediawiki-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Semediawiki-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/semediawiki-user
