19
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − <noinclude> − [[Category:Feature Page Incomplete]] − [[Category:Feature|.]] − <!-- You can add categories to tie features back to real deployments/schools requesting them, for example − [[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> − </noinclude> − − − <!-- All fields on this form are required to be accepted. − We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> − − <!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --> − Line 22:
Line 9: − + Line 48:
Line 35: − There are currently some beta version of code [https://github.com/cgueret/SemanticXO available on GitHub]+ + − ''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.'' + + + + + Line 71:
Line 63: + + + + + + + + + + + + + + +
→How To Test
== Summary ==
== Summary ==
Make use of Semantic Web technologies (for instance [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF], [http://en.wikipedia.org/wiki/Sparql SPARQL]) to enhance data management in Sugar.
Make use of Semantic Web technologies (for instance [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF], [http://en.wikipedia.org/wiki/Sparql SPARQL]) to enhance data management in Sugar.
* Targeted release: 0.98
* Targeted release: 0.98
* Last updated: {{REVISIONTIMESTAMP}}
* Last updated: {{REVISIONTIMESTAMP}}
* Percentage of completion: 40%
* Percentage of completion: 60%
== Detailed Description ==
== Detailed Description ==
== How To Test ==
== How To Test ==
All the code is available [http://git.sugarlabs.org/semanticxo on SugarLabs]
{{:{{PAGENAME}}/Testing}}
{{:{{PAGENAME}}/Testing}}
== User Experience ==
== User Experience ==
Users will eventually see that:
Users will eventually see that:
* Activities can share information
* Activities can share information
* They can directly contribute to the translation of parts of the software
* They can directly contribute to the translation of parts of the software
* They can share and link Journal entries from different instances of Sugar, even if remotely connected
* They can share and link Journal entries from different instances of Sugar, even if remotely connected
Developers of activities will have:
* An easy way to store graph-shaped data
* A query system for fetching information published in RDF, for instance those in the [http://lod-cloud.net LOD Cloud]
* A mechanism to query data from other Sugar instances
== Dependencies ==
== Dependencies ==
== Comments and Discussion ==
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
== Subpages ==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|Semantic Web]]
</noinclude>
<!-- All fields on this form are required to be accepted.
We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->