Best practices around versioning OPC files

Question

I'm interested in using OPC as a container for a new file type.  As I may wish to change my overall structure over time, I would like to include some mechanism for versioning the structure.  Is there a recommended way to do this?  (Individual files within the container already contain their own version info; it's my OPC structure I wish to version.)

At first I was going to use the Dublin Core version element in the core properties, but I assume that is really meant to indicate the file version.  I can certainly define a new file that contains version information, and perhaps reference that in a package-level relationship, but that seems a little heavy.

Answer 1

Hi Vermonster:

I have alerted the protocol documentation team regarding your inquiry on OPC file versioning. A member of the team will be in touch soon.

---

Regards, Obaid Farooqi

Answer 2

Hi vermonster,

That's an interesting question and I don't see immediately something that addresses this in ISO 29500 part 2.  Let me do some checking here and I'll get back to you.

Best regards,
Tom Jebo
Escalation Engineer
Microsoft Open Specifications

 

Answer 3

Hi vermonster,

There’s not a prescribed method for versioning in OPC. Microsoft Office uses a custom Part (app.xml) inside which it writes an AppVersion element – the content of this element and its siblings is documented in IS 29500 Part 1, 22.2.2.2 (page 4247). However, if you wish to avoid using a separate custom part then I think a good approach would be to use the version property from core properties – its definition is fairly open-ended in the standard and this seems like an appropriate use. It’s worth noting that this isn’t a Dublin Core property, it’s an OPC specific one.

Best regards,
Tom Jebo
Escalation Engineer
Microsoft Open Specifications

Answer 4

Works for me; thanks.