Oh, and I also forgot about this question ... On Donnerstag, 7. Januar 2010, Solbrig, Harold R. wrote: > Markus, > > I am trying to visualize how this information would be represented in > RDF. If we are defining predicate "X", it would seem that the "has type" > predicate would translate to "range", and "Value List" would translate > to a class named something like "X_Value_List" (since it isn't defined > as its own class - it is only defined in the context of "X"). The class > "X_value_list", in turn would then be the domain of three predicates - > "name" whose range is "String", "count" whose range is "Number" and > "source" whose domain is "Page". The response below makes it fairly > obvious that we need to be able to make "name", "count" and "source" (or > "X_name", "X_count" and "X_source"?) first class properties - otherwise > you will find yourself replicating property definitions within this > structure.
Since records (I really like having a not-so-ambiguous one-word term now!) are just position-encoded value lists of constant length, we can encode them in RDF just like containers (using numbered auxiliary properties for assigning the individual values of each component to an auxiliary element that represents the record). This is in fact what we have been doing for the old n-aries in SMW so far. For internal objects with named fields, one would really use properties so as to avoid the replication of their definition. I plan to develop a "compound types" extension for SMW that will provide a number of options for compounds (list, set, record, sub-object), but SMW 1.5.0 is first. This will then also address the request of Yaron to move records out of SMW core. Regards, Markus > > -----Original Message----- > From: semediawiki-user-boun...@lists.sourceforge.net > [mailto:semediawiki-user-boun...@lists.sourceforge.net] On Behalf Of > zehet...@molgen.mpg.de > Sent: Thursday, January 07, 2010 9:33 AM > To: mar...@semantic-mediawiki.org > Cc: semediawiki-user; semediawiki-devel; Jon Lang > Subject: Re: [Semediawiki-user] [SMW-devel] Changes for using > multi-valuedproperties > > > > Related to this is the notion of named fields. Please give the > > option > > > > to attach meaningful names to the fields for querying purposes, so > > > that the user doesn't have to specify a positional list of values. > > > For instance: > > > > > > [[has fields:: name=String; count=Number; source=Page]] > > > > > > This would allow queries for instances of the property by means of a > > > specific value for the name, property, and/or source. > > > > As I said, this task can be approached now. It is not going to be an > > extension > > of Type:List (the current favourite name of "Value list"), but another > > type > > > that allows for these inputs (how could this be called?). Thanks for > > your > > > syntax proposal; I think this is probably the most straightforward > > syntax to > > > pick. > > Another possibility, which I partly use in the SQFT extension, would be > to > supply the names via other properties on the property page which allows > different set of names for different purposes (e.g. as index replacement > in ask > queries, as table headers etc.): > > [[has fields:: String; Number; Page]] > [[has names:: name; count; source]] > [[has long_names:: official id of component; occurences between 2000 and > 2007; > first publication mentioning component]] > [[has headers:: ID by EMBL; 2000-2007 ; Publication]] > > Gu > > > ------------------------------------------------------------------------ > ------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Semediawiki-user mailing list > semediawiki-u...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- Markus Krötzsch <mar...@semantic-mediawiki.org> * Personal page: http://korrekt.org * Semantic MediaWiki: http://semantic-mediawiki.org * Semantic Web textbook: http://semantic-web-book.org --
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
