RE: Do we have to have the schemas embedded in the specification?

["chet.ensign" <chet.ensign@oasis-open.org>]

Hi Bryan, 

Forgive the brevity. I am on jury duty today and currently working on my cellphone.

The schema need not be incorporated into the narrative spec document. If it is, the practice is to put it in an appendix and include some notice or reference to the external copy. If you put it in the spec, you must include it as an external file as well. Also, in case of discrepancy, the external copy is authoritative.

A copy of the schema must be included with the spec and approved by the TC in order to be lart of the spec. In other words, you can't store the schema somewhere other than docs.oasis... and have it be official. 

It is fine to just package the schema with the spec doc and submit it it to tcadmin. We will list it on the cover  page. I can give you the url for it ahead of time if you need it.

/c

Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------

From: "Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>

Date:11/30/2014 10:49 PM (GMT-05:00)

To: "Dr. David Filip" , Yves Savourel , chet.ensign@oasis-open.org

Cc: XLIFF Main List

Subject: Do we have to have the schemas embedded in the specification?

Hi Chet,

 

Wondering if you could advise us on this?

 

Thanks,

 

Bryan

 

From: Schnabel, Bryan S
Sent: Wednesday, November 12, 2014 7:20 AM
To: 'Dr. David Filip'; Yves Savourel; chet.ensign@oasis-open.org
Cc: XLIFF Main List
Subject: RE: [xliff] Low importance: Do we have to have the schemas embedded in the specification?

 

Chet,

 

Can you advise us what the best practice is in your experience. Does OASIS have a preference? Are you aware of other TCs who remove schemas from their specification?

 

Thanks,

 

Bryan

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip
Sent: Wednesday, November 12, 2014 4:21 AM
To: Yves Savourel
Cc: XLIFF Main List
Subject: Re: [xliff] Low importance: Do we have to have the schemas embedded in the specification?

 

I think this is a question for the broader community

Implementers on the TC but also people like Spartans, Phil Ritchie, SDL, Multicorpora etc.

As editor I would be happy to get rid of this potential source of inconsistency.

However as you say the current listing are generated.

And I have to manage stage specific links anyways, so this does not save much in editing effort and IF people are using them for reading convenience, as intended, we should probably keep them...

 

No strong opinion here, happy to remove the listings if we hear from users that they are not using them..

 

Cheers

dF   

Dr. David Filip

=======================

OASIS XLIFF TC Secretary, Editor, and Liaison Officer 

LRC | CNGL | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

http://www.cngl.ie/profile/?i=452

mailto: david.filip@ul.ie

 

On Wed, Nov 12, 2014 at 11:29 AM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi all,

Do we have to have the schemas embedded in the specification document?

- They make the document a lot longer.

- It's a potential source of error since they also exist outside the specification (I know they are built automatically, but still
one could make change by accident).

- During editing you have to re-generate the specification each time you make a small change to a schema.

I think a link would be just fine.

Cheers,
-yves



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php