To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=91562
------- Additional comments from [EMAIL PROTECTED] Fri Aug 8 12:27:58 +0000 2008 ------- Hi all, the main problem that i see with copying metadata is identifying which part of the repostiory should be considered the metadata that is "connected to" some ODF element. This is not trivial because the data model of RDF (which is the standard we use for metadata) is a graph. An ODF element may be mapped to a RDF URI, by way of its xml:id attribute. So you can basically construct arbitrary structures with RDF, and all that you know about the relationship to the ODF element that is copied is the mapped URI. If you, say, only copy the RDF statements that contain the URI of the element, then you will very likely copy too little. If you, say, copy the entire strongly connected component that the URI node is part of, as well as all nodes that are reachable from this scc, then you will likely copy too much (in the limit case, the entire graph). The problem is that we (the OO.org application) do not know what the _meaning_ of the metadata is (that is kind of the point of the whole enterprise). Deleting "unused" metadata has similar issues, of course. > > ii.) the 2nd copy should point to the existing meta-data > This can not work, because the 2nd copy would have the same xml:id and a > xml:id > can be only assigned once to a certain entity. See the ODF 1.2 metadata > specification, no two ODF elements can have the same value for its xml:id > property. Well, almost; actually, the problem is that a single URI can be mapped only to a single xml:id in the manifest. The mapping between xml:id and URI is 1:1. This is (apparently) intentional. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
