{Disarmed} Re: Q on openEHR XML-schema versioning

> [Heath Frankel] > I understand your point here but if we cannot have some kind of schema > migration mechanism we will need a new schema per release, which is > something that I don't think anyone wants. Yes - I don't want that either. I bring it up because if we are allowing minor schema change

{Disarmed} Re: Q on openEHR XML-schema versioning

Hi Andrew, See below. Heath > > The question is, what do we do when we do have a data breaking schema > > change, like potentially in r1.1? I suggest that we just go with > > http://schemas.openehr.org/v1.1 and we can assume the old > > http://schemas.openehr.org/v1 meant r1.0.x. It wasn't expe

{Disarmed} Re: Q on openEHR XML-schema versioning

I can see some better schemes in the offing from the experts! I would not think we should change anything in the current schema approach, as this is a minor release. I propose to change only the version ids in the relevant schemas to reflect the small change in Base_types. We will leave it to

{Disarmed} Re: Q on openEHR XML-schema versioning

> The question is, what do we do when we do have a data breaking schema > change, like potentially in r1.1? I suggest that we just go with > http://schemas.openehr.org/v1.1 and we can assume the old > http://schemas.openehr.org/v1 meant r1.0.x. It wasn't expected to have such > a substantial sche

{Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

Q on openEHR XML-schema versioning

> Actually the namespace decision including its current format was made in > conjunction with other openEHR members including yourself and Rong as far as > I remember. Yes, sorry - wasn't trying to blame anyone :) I meant that the final decision as to what actually went into the schemas was done b

{Disarmed} Re: Q on openEHR XML-schema versioning

{Disarmed} Re: Q on openEHR XML-schema versioning Andrew Patterson wrote: ok - this approach more or less replicates the release id approach already in use, but converts it to a URL. Except, this is a change that occurs in all xml _instances_, not just the schema files. So every referen

Q on openEHR XML-schema versioning

Andrew, > There was a decision by Heath (and others at Ocean) to have a > single namespace for all the openehr XML classes around the time of the > 1.0 release. The schemaLocation of XSD files is a separate issue and one > that I would not worry about - assume that all XSD files bundled > together

{Disarmed} Re: Q on openEHR XML-schema versioning

>> Except, this is a change that occurs in all xml _instances_, not just >> the schema files. So every reference model document in every >> system in existence now has to handle two different schemas >> and convert between them. We have to decide whether this is >> what we want.. do the xml schemas

{Disarmed} Re: {Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL:

{Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL:

Q on openEHR XML-schema versioning

> ok - this approach more or less replicates the release id approach > already in use, but converts it to a URL. Except, this is a change that occurs in all xml _instances_, not just the schema files. So every reference model document in every system in existence now has to handle two different sc

Q on openEHR XML-schema versioning

Andrew Patterson wrote: >> CRs in this release have necessitated some very small (non-data >> affecting) changes in the schema BaseTypes.xsd (impact statement of >> Release 1.0.2 at >> http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candidate/publishing/release_notes_1.0.2.htm >> ;

Q on openEHR XML-schema versioning

> CRs in this release have necessitated some very small (non-data > affecting) changes in the schema BaseTypes.xsd (impact statement of > Release 1.0.2 at > http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candidate/publishing/release_notes_1.0.2.htm > ; published Release 1.0.1 schem

Q on openEHR XML-schema versioning

We are about to publish Release 1.0.2 of the openEHR specifications. The CRs in this release have necessitated some very small (non-data affecting) changes in the schema BaseTypes.xsd (impact statement of Release 1.0.2 at http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candida