On 1/20/15 11:22 AM, Paul Houle wrote:
I don't like the idea of unchecked expansion of formats because it puts an open-ended burden on both Adobe and third party software developers. If there are specific problems with the current XMP format it makes sense to transition to XMP2 but the more variation in formats the worse it will be for the ecosystem.
RDF/XML or any other XML based notation has next to no traction in regards to Linked Open Data, circa., 2015.
I am not asking Adobe to dump what they have since that in of itself puts a massive burden on them. I am suggesting a middle-ground where they simply focus on transformation between other RDF notations and the one they currently support. Net effect, we can add metadata to PDF using a variety of notations.
As for the XMP vocabulary of terms, Adobe doesn't even need to do anything about that if its published using RDF/XML. There are many transformers in place for them to leverage en route to making said vocabulary broadly readable.
Kingsley
On Mon, Jan 19, 2015 at 5:20 PM, Kingsley Idehen <[email protected] <mailto:[email protected]>> wrote:On 1/19/15 2:36 PM, Larry Masinter wrote: I just joined this list. I’m looking to help improve the story for Linked Open Data in PDF, to lift PDF (and other formats) from one-star to five, perhaps using XMP. I’ve found a few hints in the mailing list archive here. http://lists.w3.org/Archives/Public/public-lod/2014Oct/0169.html but I’m still looking. Any clues, problem statements, sample sites? Larry -- http://larry.masinter.net Larry, Rather than only supporting an XML based notation (i.e., RDF/XML) for representing RDF triples, it would be nice if one could attain the same goal (embedded metadata in PDFs) using any RDF notation e.g., N-Triples, TURTLE, JSON-LD etc.. The above would also include creating an XMP ontology that's represented in at least TURTLE and JSON-LD notations -- which do have strong usage across different RDF user & developer profiles. Naturally, Adobe apps that already process XMP simply need to leverage a transformation processor (built in-house or acquired) that converts metadata represented in TURTLE and JSON-LD to RDF/XML (which is what they currently supports).-- Regards,Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen <http://www.openlinksw.com/blog/%7Ekidehen> Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this -- Paul Houle Expert on Freebase, DBpedia, Hadoop and RDF(607) 539 6254 paul.houle on Skype [email protected] <mailto:[email protected]>http://legalentityidentifier.info/lei/lookup
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
smime.p7s
Description: S/MIME Cryptographic Signature
