Re: [Semediawiki-user] semantic properties

[<zeh...@mo...>]

Hi,

did you consider multi-value properties? 
For me they are essential in certain cases, although they have some shortcomings
within the normal SMW tools.

> So on the Dunlin page:
> Juneau Spring Abundance is = C
> Juneau Summer Abudance is = R
> Juneau Fall Abundance is = U
> Winter Abundance is = U
> Sitka Spring Abudance is = C
> Sitka Summer Abundance is = -
> Sitka Fall Abundance is = V

[[Spring Abundance::C;Juneau]]
[[Summer Abudance::R;Juneau]]
[[Fall Abundance::U;Juneau]]
[[Winter Abundance::U;?]]
[[Spring Abundance::C;Sitka]]
[[Summer Abudance::-;Sitka]]
[[Fall Abundance::V;Sitka]]

Cheers,
Gu




Quoting Matt Goff <go...@na...>:

> 
> Thanks for the suggestions.  Here's what I have so far, in terms of the
> types of things I would like to have included and what I would like to do
> with it.
> 
> The primary data-storing pages can be broadly grouped into three types:
> Species
> Location
> Habitat
> 
> Within Species I plan to store information about occurrence (spatial and
> seasonal), physical characteristics/morphology, ecology,  phenology, and
> taxonomy.  The actual mix of things will vary somewhat depending on the
> main grouping (i.e., vascular plants, birds, lichens, etc.)
> 
> Within locations I would include a description of the location as well as
> some way of locating it (lat/long, perhaps; or maybe a link to a shape
> file/map).   Each location will also be contained within more inclusive
> locations.  I'll do this both for political boundaries (town-related
> areas) and geographic areas of varying scales.  Individual locations will
> also have species lists, and ideally a given location would inherit all
> the species given for any location contained within it (though I do not
> know how easy this will be to implement).
> 
> Habitat pages I've not worked on or thought about too much yet, so I'm not
> quite sure what I would include here, but I do know that I would like to
> include species lists and some indication of species abudance within the
> habitat.
> 
> One of the big questions I have is how much to reuse the same property
> across groups of species.  For example, if I have a property called
> "GrowthForm is", for birds I might have values like "Shorebird", "Raptor",
> "Gull", "Waterfowl", etc.  For lichens I would have values like
> "Crustose", "Foliose", or "Squamulose", while for vascular plants I would
> have "Graminoid", "Herb", "Tree", or "Shrub".  In some ways it seems
> sensible to just use the same property for all the species, but in other
> ways maybe  it makes more sense to have "Bird Growth Form is", "Plant
> Growth Form is" and "Lichen Growth Form is".  I guess the tradeoff is
> between a single property with a great many allowable values or several
> properties each with a limited number of allowable values.  I'm not sure
> if  it will make a difference in the end, but one of the things I would
> like to do is create a synoptic key based on the morphological/ecological
> characteristics that are recorded.  I think this should be fairly easy to
> implement once the information is entered for all the species.  I also
> think it could a powerful application of the SMW.
> 
> Another problem I've not been able to work out is how to effectively save
> spatial/seasonal/species information both as a regional summary and for
> subareas within the region covered by my wiki.  This is most applicable to
> birds, where different species occur at different times of year.  Ideally
> I would like to be able to have seasonal presence recorded for any given
> location and season (though in practice this will probably be limited to a
> dozen or so larger areas where there is enough information available).  I
> would also like to be able to pull that information up by season,
> location, and/or species.
> 
> For example, if I consider a couple of species, I would have the following
> information:
> 
> Species:  Dunlin
>                     Sp  Su   Fa  W
> Juneau:       C   R    U   U
> Sitka:          C   -     V   +
> Ketchikan:   C   -     R   U
> 
> Species:  Common Murre
>                     Sp  Su  Fa  W
> Juneau:        F   U    F   F
> Sitka:           C   C   C   C
> Ketchikan:    C  R    C  C
> 
> (where C = Common, F= Fairly Common, U=Uncommon,  R = Rare, V= Very Rare,
> + = Casual, and - = Not known to occur)
> 
> What I would like to do is have a form where I could add multiple sections
> (perhaps using the chooser functionality) like as follows.
> 
> On the Dunlin page:
> 
> Location = Juneau
> Spring Abudance is = C
> Summer Abundance is = R
> Fall Abundance is = U
> Winter Abudance is = U
> 
> Location = Sitka
> Spring Abudance is = C
> Summer Abundance is = -
> Fall Abundance is = V
> Winter Abudance is = +
> 
> Location = Ketchikan
> Spring Abudance is = C
> Summer Abundance is = -
> Fall Abundance is = R
> Winter Abudance is = U
> 
> With the possibility of adding more locations in the same format.
> However, I don't see how to implement that (and perhaps it's not possible
> to do within the SMW framework).  So far the best I have come up with is
> that each location (or species, depending on how I set it up) would have a
> set of properties corresponding to the seasons these properties would then
> need to be included on each species (or location) page.
> 
> So on the Dunlin page:
> Juneau Spring Abundance is = C
> Juneau Summer Abudance is = R
> Juneau Fall Abundance is = U
> Winter Abundance is = U
> Sitka Spring Abudance is = C
> Sitka Summer Abundance is = -
> Sitka Fall Abundance is = V
> 
> etc.
> 
> The problem with this is that it multiplies properties pretty quickly.
> 
> Thanks,
> 
> Matt Goff
> 
> On Mon, 25 May 2009 04:33:21 -0800, Dan Bolser <dan...@gm...>
> wrote:
> 
> > Unfortunately I don't know of anything like this around at the moment
> > (other than a bunch of informal conventions that you will pick up
> > reading various documents). Semantic Forms imposes a set of
> > conventions which are useful, so I would recommend reading the
> > documentation for that. I've been meaning to write a 'data modelling
> > howto' for ages now, shamefully I haven't even started.
> >
> > I would suggest that you write one document briefly summarising the
> > data that you have and how you intend to map it onto SMW (category
> > names, property names, pages and queries). This is the first step in
> > any basic 'data modelling' or 'requirements analysis' strategy.
> >
> > Post that summary back to the list, and I'm guessing people will pipe
> > up with some suggestions about the sorts of names or conventions that
> > they would use.
> >
> > The next most important thing to do is think about how you expect your
> > site to be used, and to check if you design will support that usage.
> > Also you should look at a selection of the sites listed at
> > http://smw.referata.org and see how things are done there.
> 
> 
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
> _______________________________________________
> Semediawiki-user mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>