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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: Groups - XLIFF Teleconference added

Same agenda as last time. Not enough people on the last call. But we did
ave a good discussion about trying to publish errata instead of XLIFF

 -- Bryan Schnabel*

XLIFF Teleconference has been added by Bryan Schnabel*

Date:  Tuesday, 18 August 2009
Time:  11:00am - 12:00pm ET

Event Description:
1/ Call one of the FreeConferenceCall phone numbers:
US: (712) 432-1600
US: (605) 772-3100
Austria: 0820 4000 1552
Belgium: 070 35 9974
France: 0826 100 256
Germany: 01805 00 76 09 
Ireland: 0818 270 021
Italy: 848 390 156
Netherlands: 0870 001 920
Spain: 902 886025
Switzerland: 0848 560 179
Note: new number for UK
UK: +44 (0) 844 581 9102
UK: 0870 35 204 74 (will redirect to new number for 90 days, from Aug 6)
2/ Enter the Participant Access Code: 737043#

1/ Roll call
2/ Approve July 07, 2009 meeting minutes:
   Accept, reject, or amend.

3/ XLIFF 1.2(.1) Errata vs. New Rev.: The word Errata is spoken often in our TC meetings. We previously concluded that the bug fixes in the XLIFF 1.2 spec and schemas were substantive, thereby ruling out the possibility to publish Errata (per the rules and definitions of OASIS). Here's the email that summarized that (http://lists.oasis-open.org/archives/xliff/200808/msg00005.html). Perhaps the TC now thinks Errata is an option. Is it?  From the OASIS policy (http://www.oasis-open.org/committees/process.php#errata):

  A. Define Errata: "Errata" means a set of changes or proposed changes to a specification that are not Substantive Changes.

  B. Define Substantive Change: "Substantive Change" is a change to a specification that would require a compliant application or implementation to be modified or rewritten in order to remain compliant.
  C. XLIFF 1.2 changes to Spec and Schema: do these require an XLIFF 1.2 compliant application/implementation to be modified to remain compliant?
   i.  Yes = Publish new rev (1.2.1), no Errata document is published
   ii. No = Publish Errata

4/ XLIFF 1.2.1 must now be moved to "front burner" now that errors have been identified in the samples

Example of a conformance clause: DITA (http://lists.oasis-open.org/archives/dita/200907/msg00123.html)
  A. Good news, Schemas, Samples, and Spec are all fixed and ready to be voted on

  B. We must include a conformance clause in order to bring XLIFF 1.2.1 to ballot
     i.  Do we create a very lax conformance clause for 1.2.1, and go back to working on 2.0? And move the work to email?
     ii. Do we create a robust conformance clause in order to have a good starting point for 2.0's clause?

  C. Bryan posted the OASIS guidelines (http://lists.oasis-open.org/archives/xliff/200907/msg00017.html)

  D. Rodolfo posted a first draft to start the discussion (http://lists.oasis-open.org/archives/xliff/200907/msg00018.html)

  E. Doug made a suggestion, representing the CMS perspective (http://lists.oasis-open.org/archives/xliff/200907/msg00019.html)

  F. After a few refining emails, Rodolfo posted a draft on the wiki (http://wiki.oasis-open.org/xliff/XLIFF1.2/Errata), item 7

  G. Magnus documented that it might be more efficient to create a list of thing that do not need to be preserved. He proposed that given our timing goals for XLIFF 1.2.1, we should leave the application compliance undefined and focus on file compliance only, with a view to properly define application compliance in scope of XLIFF 2.0. (http://lists.oasis-open.org/archives/xliff/200907/msg00023.html)

  H. Lucia recommended putting brackets and spec-section-titles into the clause

5/ Review Requirements for inline elements [define, understand, then vote - being mindful of Tony's suggestion of limiting the length of discussion]
(come to consensus on the requirements, then assign owners to propose wording for the spec)    

{here's my *score card*:

1.1. Definitions/Terminology
"This section is under construction. " (additional examples have been added)

 3.1.1. Common representation of 'inline' markup vs 'block-level' markup
   1. [Resolved]
   2. [Resolved]
   3. [Not Resolved]
 3.1.2. Canonical Representation of native content
   [Not Resolved - Christian annotated a distinction:
   "Maybe, we may want to differentiate between two types of canonical representation:"
	1. a semantic/abstract one
	2. an encoded/concrete one]
 3.1.3. Extensibility / Annotations
   ["Christian will modify item 3.1.3 and separate extensibility 
     from annotations. Action item: Christian to extend the text 
     to clarify the scope and meaning of the request.]
 3.1.4. [Resolved] Content Manipulation
 3.1.5. [Not yet addressed] XML Implementation 
 3.1.6. [Not yet addressed] General Scope}

6/ If something is valid XML and not disallowed explicitly by the specification, it means it is allowed?(http://lists.oasis-open.org/archives/xliff/200906/msg00008.html) (Question captured from Yves' comment on Rodolfo's XLIFF Checker Tool)

7/  "XLIFF 2.0 will be complete when _______" 
  There are two camps for filling in the blank
  A. Set a calendar goal. All items that are complete and approved by the 
     TC make it into XLIFF 2.0 - All others need to wait for the "next train," 
     i.e., XLIFF 2.X or XLIFF 3. Special care needs to be taken to define 
     doneness and ensure no dependency issues between items. 
     And "XLIFF 2.0 is complete on set date of *Month/Day/Year*"
         - or - 
 B. Define a finite set of XLIFF 2.0 items. Set a cutoff date for adding items. 
    The list of accepted items becomes our requirements document.
    And "XLIFF 2.0 is complete when items 1 through X are finished"
    (some in this camp see our current set of goals, as is, as that 
    finite list)

    i. Yves commented that XLIFF is not a software. And we should be careful with releasing versions that do not have some specific features we know will ultimately end up there. (http://lists.oasis-open.org/archives/xliff/200904/msg00018.html)
8/ XLIFF 2.0 


View event details:

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web

PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-WR-CALNAME:My Calendar
SUMMARY:XLIFF Teleconference
DESCRIPTION:1/ Call one of the FreeConferenceCall phone numbers:\nUS: (712)
  432-1600\nUS: (605) 772-3100\nAustria: 0820 4000 1552\nBelgium: 070 35
  9974\nFrance: 0826 100 256\nGermany: 01805 00 76 09 \nIreland: 0818
  270 021\nItaly: 848 390 156\nNetherlands: 0870 001 920\nSpain: 902
  886025\nSwitzerland: 0848 560 179\nNote: new number for UK\nUK: +44
  (0) 844 581 9102\nUK: 0870 35 204 74 (will redirect to new number for
  90 days\, from Aug 6)\n \n2/ Enter the Participant Access Code:
  737043#\n\nGroup: OASIS XML Localisation Interchange File Format
  (XLIFF) TC\nCreator: Bryan Schnabel*

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