From: Alex M. H. <ont...@on...> - 2010-02-12 20:47:07
|
Hello, As I'm adding more content to a system I'm building, I have noticed that properties on embedded pages are starting to "trickle up" to the pages on which they are embedded. Example: ---Page A--- [[A::B]] embeds Page X via query ---Page X--- [[Y::Z]] A query for [[Y::+]] or [[Y::Z]] returns both Page A and Page X. I suppose one workaround would be to <noinclude> the marked up text on Page X, and <includeonly> a version that retains the wiki links, but not the semantic data (this way, people can still click on hyperlinks in the embedded text on Page A). Is there a more elegant solution that would not require essentially doubling the data in the system? For example: Would it be possible to exclude from queries these "trickle up" properties--as a general rule, that is, not by specifically excluding the offending property, e.g., a __NOEMBEDDEDPROPERTIES__ magic word (or something like that) for Page A, that would still retain Page A's semantic data? I'm using MW 1.15.1, SMW 1.4.3, and SMWHalo 1.4.6. Any ideas/suggestions would be most appreciated. Thanks, Alex -- Alex M. Hendler ontolawgy(tm) LLC http://ontolawgy.com |
From: Alex M. H. <ont...@on...> - 2010-02-13 08:09:30
|
Found a workaround; please let me know if you'd like any details (no need to spam the list). -Alex ------- Original message ------- From: "Alex M. Hendler" <ont...@on...> To: "sem...@li..." <sem...@li...> Cc: Subject: How to prevent property "creep" or "trickle-up"? Date: Friday, February 12, 2010 23:38:58 GMT+03:00 > Hello, > > As I'm adding more content to a system I'm building, I have noticed that > properties on embedded pages are starting to "trickle up" to the pages > on which they are embedded. > > Example: > > ---Page A--- > > [[A::B]] > > embeds Page X via query > > ---Page X--- > > [[Y::Z]] > > > A query for [[Y::+]] or [[Y::Z]] returns both Page A and Page X. > > I suppose one workaround would be to <noinclude> the marked up text on > Page X, and <includeonly> a version that retains the wiki links, but not > the semantic data (this way, people can still click on hyperlinks in the > embedded text on Page A). > > Is there a more elegant solution that would not require essentially > doubling the data in the system? > > For example: Would it be possible to exclude from queries these "trickle > up" properties--as a general rule, that is, not by specifically > excluding the offending property, e.g., a __NOEMBEDDEDPROPERTIES__ magic > word (or something like that) for Page A, that would still retain Page > A's semantic data? > > I'm using MW 1.15.1, SMW 1.4.3, and SMWHalo 1.4.6. > > Any ideas/suggestions would be most appreciated. > > Thanks, > Alex > -- > Alex M. Hendler > ontolawgy(tm) LLC > http://ontolawgy.com |