Thanks for clarifying that Michael. Well, then I give up :) XMP looks ridiculous indeed. If normal RDF/XML was allowed, it could be actually useful. On Jan 20, 2015 9:28 AM, "Michael Brunnbauer" <bru...@netestate.de> wrote:
> > Hello Martynas, > > On Tue, Jan 20, 2015 at 02:34:23AM +0100, Martynas Jusevi??ius wrote: > > IMO mixing RDF/XML with JSON doesn't make sense. > > This is not RDF/XML. This is XMP. The last time I looked, XMP was a > ridiculously crippled version of RDF/XML: > > > http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf > > "The rdf:about attribute on the rdf:Description element is a required > attribute that may > be used to identify the resource whose metadata this XMP describes. The > value of this > attribute should generally be empty." > > "The XMP storage model does not use the rdf:about attribute to identify > the > resource. The value will be preserved, but is not meaningful to XMP." > > "All rdf:Description elements within an rdf:RDF element must have the > same value for their rdf:about attributes." > > "The elements immediately within rdf:RDF must be rdf:Description > elements." > > "The rdf:ID and rdf:nodeID attributes are ignored." > > "Top-level RDF typed nodes are not supported." > > I guess this is why people here think about using a serialized RDF document > as value of a property - which multiplies the ridiculousness created by > Adobe. > > I would not recommend such stunts if we want to be taken seriously. > > Regards, > > Michael Brunnbauer > > -- > ++ Michael Brunnbauer > ++ netEstate GmbH > ++ Geisenhausener Straße 11a > ++ 81379 München > ++ Tel +49 89 32 19 77 80 > ++ Fax +49 89 32 19 77 89 > ++ E-Mail bru...@netestate.de > ++ http://www.netestate.de/ > ++ > ++ Sitz: München, HRB Nr.142452 (Handelsregister B München) > ++ USt-IdNr. DE221033342 > ++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer > ++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel >