Features/Semantic Web: Difference between revisions

Cgueret (talk | contribs)
Cgueret (talk | contribs)
No edit summary
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 -->
== 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.
Line 72: Line 59:
== 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. -->
<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 -->