OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: manifest


Re: this from Patrick's minutes:

> Pending item: How to add more information to the manifest file, embed
> in existing file or add more files. Rob, this should be one of the
> last things we figure out. Adobe may have been extending the manifest
> already. OCF, Open Container Format.

As I mentioned on the main list, I think what we need and what the OCF 
people need are the same: some way to add a type or a class to a 
package file, to declare the root (this is the OCF thing; not sure why 
they need this), and to have some more general extensibility.

I would to see us resolve at least the technical issue of how we'd 
propose to do it.

For example, do we just propose a manifest:class attribute or some such?

That way we can do:

<manifest:file-entry
	manifest:class="metadata"
	manifest:role="citation"
	manifest:media-type="application/rdf+xml"
	manifest:href="bibliography.xml"/>

Am just throwing an idea at the wall (values could instead be URIs), 
but I think something like this covers our needs and also OCFs. It 
makes it easy, for example, for a plug-in to register a link between a 
custom field and a metadata file.

Thoughts?

Bruce



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]