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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Nov-13-2012 - Summary


XLIFF Inline Markup Subcommittee Teleconference - Nov-13-2012 - Summary

Present: Fredrik, Yves
Regrets: Alan


=== Type attribute.

We have a proposed change for the type attribute for inline codes
(based on the discussion during the face-to-face)
Summary is here:
https://lists.oasis-open.org/archives/xliff-inline/201210/msg00013.html

We have a proposed list for the top-level type and for the 'xlf:' defaults for the sub-type.

Y: Since there are no dissents and the change match the F2F meeting wishes we can assume this is fine.
F: yes, I prefer the old way, but ok with this.
Y: same here.

ACTION ITEM: Update spec to reflect the type/subtype change


=== Names.

If anyone would like to use different names for our elements and attributes, make sure to provide that info.
This email points to the shared document for this:
https://lists.oasis-open.org/archives/xliff-inline/201210/msg00012.html

F/Y discussed the possible renaming.
Conclusion: nid->dataRef, nidStart->daatRefStart, nidEnd->dataRefEnd, rid->scRef

ACTION ITEM: Yves to post email for new names proposal.



=== Draft.

Latest draft is here:
https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/xliff-core.pdf
Are we ready to submit the draft to the TC?
we need to approve it from within the TC first.

Y: Are we ready?
F: Yes I think so. we may have a few changes at the TC level.
.. but what we have should be working for our requirements
.. and we need broader base to discuss the remaining issues (like interaction between inline and non-inline elements)

ACTION: Post an email seeking consensus for the current draft
If we do have the consensus: propose the draft to the TC.


=== Any other business

PR for mrk/ref:

"When a user agent removes a <mrk> element or a pair of <sm> / <em> elements and the ref attribute
is present, it must check whether or not the URI pointed by the ref attribute is within the same
<unit> as the removed element. If it is and no other element has a reference to the pointed element,
the user agent must remove the pointed element."

F: would prefer to not remove referred elements.
.. PR should be at the referred element level.

-> need to reword
ACTION ITEM: Yves to post an email on this.

F: for modules: need 2 sets of PRs
- for core-only tools
- for supporting tools


-end




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