Revisions for LanguageSpecificStructuredStringType

RevisionTermsStatus
Saved 06/17/2019 - 21:49 by wendy

corrected typo in documentation

Proposal current revision (published)
Saved 07/16/2018 - 15:38 by wendy

tc-43 changed isStructuredBy to structureUsed to resolve property name conflict with all StructuredCollections

Proposal archived
Saved 07/12/2018 - 17:52 by wendy

changed isStructuredBy target to StringStructureType and added example

Proposal archived
Saved 07/12/2018 - 17:39 by wendy

TC-44 changed to extention of LanguageSpecificString added isStructuredBy and otherDefined

Proposal archived
Saved 07/12/2018 - 17:21 by wendy

TC-44 adding scope and documentaiton

Proposal archived
Saved 04/09/2018 - 22:23 by wendy

made property for editing

Proposal archived
Saved 03/07/2018 - 17:45 by wendy

removed temp isProperty check

Proposal archived
Saved 03/07/2018 - 17:41 by wendy

added type to name TC-41

Proposal archived
Saved 03/07/2018 - 17:26 by wendy

temp isProperty

Proposal archived
Saved 11/22/2017 - 18:52 by wendy

property name changed back to content as this is required for XML binding transformation

Proposal archived
Saved 08/04/2017 - 16:36 by wendy

changed content to formattedContent per DMT-132

Proposal archived
Saved 02/14/2017 - 20:56 by wendy

removed property

Proposal archived
Saved 02/14/2017 - 20:53 by wendy

made complex in order to edit parent complex data type

Proposal archived
Saved 02/14/2017 - 20:50 by wendy

changed name per DMT-79

Proposal archived
Saved 06/15/2016 - 23:34 by wendy

test of property issue solution

Proposal archived
Saved 08/14/2015 - 17:41 by wendy

Uniform use of property language

Proposal archived
Saved 11/28/2014 - 14:49 by oleg.volguine

renamed "xml:lang" property to "xmlLang"

Proposal archived
Saved 11/28/2014 - 13:01 by oleg.volguine

changed cardinality on the 'content' property from 0..n to 1..n to ensure this property is present as it contains the actual value of the Content object

Proposal archived
Saved 11/28/2014 - 12:30 by wendy

renamed 'value' property to 'content' inline with modelling team rules and changed cardinality from 0..n to 1..n as at least one property 'content' is required.

Proposal archived
Saved 11/27/2014 - 17:28 by jannik

changed the property name from 'xhtmlBlkNoFormMix' to 'value' to make it more user friendly and understandable

Proposal archived
Saved 11/27/2014 - 16:04 by oleg.volguine

chnanged the cardinality on the translationSourceLanguage from 0..1 to 0..n to match the description.

Proposal archived
Saved 11/26/2014 - 11:27 by jon
Proposal archived
Saved 11/25/2014 - 11:57 by oleg.volguine

Content - added xml:lang datatype to translationSourceLanguage - fixed property names to remove non-alpha character ';' and '.' - for translationSourceLanguage consider changing either the cardinality from 0..1 to 0..n in order to match the description which talks about multiple languages OR change the description to just one language (Content with multiple source languages would be very difficult to translate, would be better to break up content with multiple source languages into multiple Content objects with single source language)

Proposal archived
Saved 11/25/2014 - 11:50 by oleg.volguine
Proposal archived
Saved 11/25/2014 - 10:34 by marcel
Proposal archived
Saved 05/29/2014 - 21:21 by Franck
Proposal archived
Saved 05/29/2014 - 21:12 by Franck
Proposal archived
Saved 05/23/2014 - 13:58 by ddi4
Proposal archived