Difference (from prior revision)
Changed: 409c409,410
|
MarkGreaves: Tim: I agree that we will need KEs in many cases; the question is the degree to which semantic wikis can socialize some of the lower-end schema design applications. {nid 1URP} |
|
MarkGreaves: Tim: I agree that we will need KEs in many cases; the question is the degree to which semantic wikis can socialize some of the lower-end schema design applications. {nid 1URP} |
Changed: 752c753,755
|
EdDodds: Isolated components will be available to link with electronic medical records and financial reporting increasingly done in extensible business reporting language (xbrl) as well. Anyone looking at the medical banking implications of this yet? {nid 1UTZ} |
|
EdDodds: Isolated components will be available to link with electronic medical records and financial reporting increasingly done in extensible business reporting language (xbrl) as well. Anyone looking at the medical banking implications of this yet? {nid 1UTZ} |
Changed: 1347c1350,1351
|
MarkusKroetzsch: @DanielSchwabe: The people from the street care about the label "wiki" as they care about "Web 2.0", but the cateogrization as one or the other type of CMS is not essential to them as long as it works {nid 1UXP} |
|
MarkusKroetzsch: @DanielSchwabe: The people from the street care about the label "wiki" as they care about "Web 2.0", but the cateogrization as one or the other type of CMS is not essential to them as long as it works {nid 1UXP} |
Changed: 1449c1453,1455
|
For instance, from my experience working within the biomedical domain I have see that tools such as WIKI-Proteins do not facilitate any specific tool for the kind of information they are meant to support. How could having more specific UIs help solving the UI problem? {nid 1UYC} |
|
For instance, from my experience working within the biomedical domain I have see that tools such as WIKI-Proteins do not facilitate any specific tool for the kind of information they are meant to support. How could having more specific UIs help solving the UI problem? {nid 1UYC} |
Changed: 1453c1459,1460
|
BobbinTeegarden: Has anyone tried to move the wiki ui from words and bullets to an interactive graph (with GIS overlay) more like Gelernter's Mirror World? {nid 1UYD} |
|
BobbinTeegarden: Has anyone tried to move the wiki ui from words and bullets to an interactive graph (with GIS overlay) more like Gelernter's Mirror World? {nid 1UYD} |
Changed: 1473c1480,1483
|
HaroldSolbrig: @Sebastian: Even with owl:sameAs, we still have to get folks from whatever historical or language specific hyperlink they've got to the SMW page that defines the category or property. The advantage of the identifier approach is we don't have to carry a history of all names that have been used. {nid 1UYI} |
|
HaroldSolbrig: @Sebastian: Even with owl:sameAs, we still have to get folks from whatever historical or language specific hyperlink they've got to the SMW page that defines the category or property. The advantage of the identifier approach is we don't have to carry a history of all names that have been used. {nid 1UYI} |
Changed: 1494c1504,1505
|
SebastianSchaffert: @Harold: that's fine - my concern is only that it is not so easy to use the same concept in multiple languages {nid 1UYN} |
|
SebastianSchaffert: @Harold: that's fine - my concern is only that it is not so easy to use the same concept in multiple languages {nid 1UYN} |