19 Nov 2011 12:14
evolution?
Hi all, I have already briefly spoken with Johannes about this some time ago, but I like to update XEP-0244 to for two reasons: 1. tighten the XML Schema support by denoting the expected root element 2. support Resource Description Framework payload About 1 The current proposal specifies which schema payload should comply to, e.g. in Example 5. However, with large schemas it becomes increasingly easy to pick the wrong part of the schema, and still get useless input. That is, in that particular example, we service can get a crystal, molecule, list of molecules, whatever... I think that example should be updated to indicating an exact root element Task: update Example 5 About 2 This is trickier. There might very well be an XML Schemata for RDF/XML, but that is not enough. We also need to indicate the rdf:type or rdfs:subClassOf of the in and out. We need both of them, to service the two common options to represent a concept in RDF, as a class (rdfs:subClassOf) or as an instance (rdf:type). We can require RDF/XML to limit introducing the need for new libs or parsing grammars, but we need to update the following (and for <out> likewise):(Continue reading)
RSS Feed