Rosetta Code:Add a Task: Difference between revisions
Content added Content deleted
(→Extreme Language: Solidify language) |
(→Semantic annotations: Example of semantic linkage.) |
||
| Line 45: | Line 45: | ||
==Additional information== |
==Additional information== |
||
===Semantic annotations=== |
===Semantic annotations=== |
||
If your task invokes particular concepts (and it should; that's part of what a task is supposed to do), these should be marked with semantic notation. This will help better organize your task on Rosetta Code. |
If your task invokes particular concepts (and it should; that's part of what a task is supposed to do), these should be marked with semantic notation. This will help better organize your task on Rosetta Code. To take an example, excerpted and modified from [[Delegates]]: |
||
<blockquote>A delegate is a helper object used by another object. The delegator may send the delegate certain messages, and provide a default implementation when there is no delegate or the delegate does not respond to a message.</blockquote> |
|||
<!-- Need examples! --> |
|||
This could be annotated like this: |
|||
<blockquote>A delegate is a <nowiki>[[task concept::helper object]]</nowiki> used by another object. The delegator may send the delegate certain <nowiki>[[task concept::message|messages]]</nowiki>, and provide a default implementation when there is no delegate or the delegate does not respond to a message.</blockquote> |
|||
This links the task with a property named "task concept" using "helper object" and "message" as the relation. |
|||
===Lurk!=== |
===Lurk!=== |
||