Temlakos wrote:
> Jon:
>
>  Your proposal sounds like one for a virtual page of some kind--say, a
>  "page" that is actually a section, not a true page.

Essentially, yes.  Perhaps this could be done by having you append an
anchor name to any property that applies to the subject of a section
instead of applying to the main subject of the page.  As long as there
are any "section properties" on the page, that section's anchor counts
as a "virtual page" for semantic purposes.

E.g., you might have a section under Eris entitled "Dysnomia"; in that
section (or elsewhere on the page, as appropriate), you might include
the text '[[Celestial class#Dysnomia::Moon]]', to semantically
indicate that Dysnomia is a moon.  Elsewhere on the same page, you
might say '[[Celestial class::Dwarf Planet]]' to semantically indicate
that Eris is a dwarf planet.

For semantic purposes, Eris and Eris#Dysnomia would be considered to
be separate pages, with Eris having the property 'Celestial class'
with the value 'Dwarf Planet', and Eris#Dysnomia having the property
'Celestial class' with the value 'Moon'.  A query for all moons on the
site would include a link to 'Eris#Dysnomia', but not to 'Eris'
itself.

>  Or for a better example, check out:
>
>  <http://creationwiki.org/index.php/Pluto>
>
>  and Pluto's satellites:
>
>  <http://creationwiki.org/index.php/Charon>
>  <http://creationwiki.org/index.php/Nix>
>  <http://creationwiki.org/index.php/Hydra_(moon)>
>
>  Same sort of problem. Nix and Hydra don't truly rate a separate
>  page--but how else can I use an inline query to produce a table of
>  Pluto's satellites? And I'd say that Charon /does/ rate a separate page.
>
>  I haven't even mentioned the planet Jupiter, which has /sixty-three/
>  satellites at last count--because I have only begun to write articles
>  about Jovian moons, starting with Galileo's initial discoveries. Now
>  maybe a few of the innermost moons rate separate pages--but all
>  sixty-two? And how about Saturn? Sure, I can write articles about Titan
>  (already done), Rhea, Mimas, Iapetus, etc.--but must I write a page
>  about every little ring shepherd? And I don't even want to think about
>  annotating the asteroids.

:shudder: That's a Herculean task no matter how you go about it.

>  If we /could/ establish a "virtual page," then a property of the Page
>  type could point either to a virtual page or to a real page.

If we go with something like my "attach annotations to anchors" idea
above, this becomes a non-issue: to point a Page-type property to a
virtual page, point it to the virtual page's anchor.

Things get a little messy when you start considering page redirects;
for instance, what happens when someone discovers enough information
about Dysnomia to justify a page of its own, but you've already got a
dozen links pointing to the anchor-based "virtual page"?

>  This might require yet another database table, say "smw_virtual_pages."
>  This table would have at least two columns: one with the virtual page
>  name, and the other with a page-and-section resolution that would have
>  exactly the same syntax as a section-specific redirection.

I'm not (yet) familiar with how the database is set up; is there
anything that forbids hash-marks in page names?

-- 
Jonathan "Dataweaver" Lang

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to