|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| Category | see §4.2.2 of rfc 4287. |
| Content | see §4.1.3 in rfc 4287 One way to think of this is as a class that represents what one can get from an HTTP connection. |
| Entry | see §4.1.2 of the rfc 4287 spec |
| Feed | Container for feed metadata. |
| FeedOrEntry | Union of the Feed and Entry class. |
| FeedOrEntryOrLink | |
| Generator | see §4.2.4 of rfc 4287 spec. |
| GeneratorOrPerson | |
| HTML | see §3.1.1.2 of rfc 4287. |
| Link | see §4.2.7 of rfc 4287 spec. |
| Person | see §3.2 of rfc 4287 spec. |
| PlainText | see §3.1.1.1 of rfc 4287. |
| RelationType | see §4.2.7.2 of rfc 4287. |
| TextContent | see §3.1 of rfc 4287. |
| Version | Metadata about the state of a resource with given :id at an :updated time. |
| XHTML | see §3.1.1.3 of rfc 4287. |
| XML | see §4.1.3.3 of rfc 4287. |
The AtomOWL ontology is inspired from the work done by the atom working group. This ontology is working off the rfc 4287 published among othe places at http://www.atompub.org/rfc4287.html . The AtomOWL ontology uses as much as possible the same terms as the format there to make the relation easy to understand. The AtomOWL name space is slightly different from the atom namespace [see post http://www.imc.org/atom-syntax/mail-archive/msg16476.html]. But this is a good thing as it helps distinguish the ontology from the rfc 4287 serialisation.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||