For the purpose of developing future products, RDFS/OWL XML files are to be considered pretty much dead and gone.

They require too much work to express concepts that a custom built solution based on custom text formats would express better, while keeping the data more readable and editable to humans and machines alike. They add no real value and only make life a little more miserable for everybody that stumbles on them. (and has to deal with their namespace nomenclature)

There are gigantic document handling solutions though, recently developed, deployed, and in current service, that threaten to linger around for a very long time, making those files the best candidate for the Best WTF for the next generation.

Microdata systems, (the validator-friendly version of microformats) like those described in schema.org, present instead a lot of advantages for developers, editors, and readers, alike; both human or mechanical.

RDF concepts can be mapped (and are actually being explicitly mapped) over microdata representations painlessly.

Microdata items allow authors and document handling systems to enrich communication in a way that's pretty easy (as easy as CSS or DOM) to handle and customize for the reader.

For the purpose of developing future products, RDFS/OWL XML files are to be considered pretty much dead and gone.

They require too much work to express concepts that a custom built solution based on custom text formats would express better, while keeping the data more readable and editable to humans and machines alike. They add no real value and only make life a little more miserable for everybody that stumbles on them. (and has to deal with their namespace nomenclature)

There are gigantic document handling solutions based on them, though, and they were recently developed, deployed, and are in current service. They threaten to linger around for a very long time. Many programmers in the future will undoubtedly suffer from many RDF-and-OWL-inducted WTFs.

Microdata systems, (the validator-friendly version of microformats) like those described in schema.org, present instead a lot of advantages for developers, editors, and readers, alike; both human and mechanical.

RDF concepts (those worth saving) can be mapped (and are actually being explicitly mapped) over microdata representations painlessly.

Microdata items allow authors and document handling systems to enrich communication in a way that's pretty easy (as easy as CSS or DOM) to handle and customize for the reader.

For the purpose of developing future products, RDFS/OWL XML files are to be considered pretty much dead and gone.

They require too much work to express concepts that a custom built solution based on custom text formats would express better, while keeping the data more readable and editable to humans and machines alike. They add no real value and only make life a little more miserable for everybody that stumbles on them. (and has to deal with their namespace nomenclature)

Microdata systems, (the validator-friendly version of microformats) like those described in schema.org, present instead a lot of advantages for developers, editors, and readers, alike; both human or mechanical.

For the purpose of developing future products, RDFS/OWL XML files are to be considered pretty much dead and gone.

They require too much work to express concepts that a custom built solution based on custom text formats would express better, while keeping the data more readable and editable to humans and machines alike. They add no real value and only make life a little more miserable for everybody that stumbles on them. (and has to deal with their namespace nomenclature)

There are gigantic document handling solutions though, recently developed, deployed, and in current service, that threaten to linger around for a very long time, making those files the best candidate for the Best WTF for the next generation.

Microdata systems, (the validator-friendly version of microformats) like those described in schema.org, present instead a lot of advantages for developers, editors, and readers, alike; both human or mechanical.

RDF concepts can be mapped (and are actually being explicitly mapped) over microdata representations painlessly.

Microdata items allow authors and document handling systems to enrich communication in a way that's pretty easy (as easy as CSS or DOM) to handle and customize for the reader.