[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl] Consistency in code type name property primary noun
yes,
<Value ColumnRef="PropertyTermPossessiveNoun">
<SimpleValue>Guarantee Type</SimpleValue>
<Value ColumnRef="PropertyTermPrimaryNoun">
<SimpleValue>Code</SimpleValue>
<Value ColumnRef="PropertyTerm">
<SimpleValue>Guarantee Type Code</SimpleValue>
<Value ColumnRef="RepresentationTerm">
<SimpleValue>Code</SimpleValue>
- is correct and the first (and last) sample are not. we always needs
the Property Term to contain "Code"
so we should be reporting as an error all rows of Data Type "Code. Type"
where the Property Term Primary Noun /does not contain "Code" as the
last term/, so they can be repaired to be consistent. The distinction
between PropertyTermPossessiveNoun and PropertyTermPrimaryNoun is subtle
and grammatical and not necessary for CCTS - so we can be lax on if some
entries have confused the two. The important thing is that the
combination of PropertyTermPossessiveNoun and PropertyTermPrimaryNoun
(that makes the entire PropertyTerm) is globally unique in the UBL library.
G. Ken Holman wrote:
> Hi folks,
>
> I'm now preparing the cl/gc/templates/ directory, and I've come across
> an inconsistency that I'm not sure is intentional or not.
>
> The issue is whether or not the Property Term Primary Noun is obliged
> to be "Code" for items of data type "Code. Type".
>
> First, I think the following is not intentional and one of these two
> have to be fixed:
>
> <Value ColumnRef="UBLName">
> <SimpleValue>GuaranteeTypeCode</SimpleValue>
> </Value>
> <Value ColumnRef="DictionaryEntryName">
> <SimpleValue>Guarantee Certificate. Guarantee Type.
> Code</SimpleValue>
> </Value>
> <Value ColumnRef="ObjectClass">
> <SimpleValue>Guarantee Certificate</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPossessiveNoun">
> <SimpleValue>Guarantee</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPrimaryNoun">
> <SimpleValue>Type</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTerm">
> <SimpleValue>Guarantee Type</SimpleValue>
> </Value>
> <Value ColumnRef="RepresentationTerm">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="DataType">
> <SimpleValue>Code. Type</SimpleValue>
> </Value>
>
> ... and:
>
> <Value ColumnRef="UBLName">
> <SimpleValue>GuaranteeTypeCode</SimpleValue>
> </Value>
> <Value ColumnRef="DictionaryEntryName">
> <SimpleValue>Financial Guarantee. Guarantee Type Code.
> Code</SimpleValue>
> </Value>
> <Value ColumnRef="ObjectClass">
> <SimpleValue>Financial Guarantee</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPossessiveNoun">
> <SimpleValue>Guarantee Type</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPrimaryNoun">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTerm">
> <SimpleValue>Guarantee Type Code</SimpleValue>
> </Value>
> <Value ColumnRef="RepresentationTerm">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="DataType">
> <SimpleValue>Code. Type</SimpleValue>
> </Value>
>
> ... where both have the same UBL name but different name components.
> This one was reported in my error report last night.
>
> But, what about the differences between two different reason codes
> where the first one has the property term primary noun of "Code":
>
> <Value ColumnRef="UBLName">
> <SimpleValue>AdjustmentReasonCode</SimpleValue>
> </Value>
> <Value ColumnRef="DictionaryEntryName">
> <SimpleValue>Forecast Revision Line. Adjustment Reason
> Code. Code</SimpleValue>
> </Value>
> <Value ColumnRef="ObjectClass">
> <SimpleValue>Forecast Revision Line</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPossessiveNoun">
> <SimpleValue>Adjustment Reason</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPrimaryNoun">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTerm">
> <SimpleValue>Adjustment Reason Code</SimpleValue>
> </Value>
> <Value ColumnRef="RepresentationTerm">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="DataType">
> <SimpleValue>Code. Type</SimpleValue>
> </Value>
>
> ... but the second one does not:
>
> <Value ColumnRef="UBLName">
> <SimpleValue>PreviousCancellationReasonCode</SimpleValue>
> </Value>
> <Value ColumnRef="DictionaryEntryName">
> <SimpleValue>Process Justification. Previous_ Cancellation
> Reason. Code</SimpleValue>
> </Value>
> <Value ColumnRef="ObjectClass">
> <SimpleValue>Process Justification</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermQualifier">
> <SimpleValue>Previous</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPossessiveNoun">
> <SimpleValue>Cancellation</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTermPrimaryNoun">
> <SimpleValue>Reason</SimpleValue>
> </Value>
> <Value ColumnRef="PropertyTerm">
> <SimpleValue>Cancellation Reason</SimpleValue>
> </Value>
> <Value ColumnRef="RepresentationTerm">
> <SimpleValue>Code</SimpleValue>
> </Value>
> <Value ColumnRef="DataType">
> <SimpleValue>Code. Type</SimpleValue>
> </Value>
>
> So my question is, should I be reporting as an error all rows of Data
> Type "Code. Type" where the Property Term Primary Noun is not "Code",
> so they can be repaired to be consistent?
>
> Thank you for your guidance.
>
> . . . . . . . . . . Ken
>
> --
> XSLT/XQuery training: after http://XMLPrague.cz 2011-03-28/04-01
> Vote for your XML training: http://www.CraneSoftwrights.com/o/i/
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com
> Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/o/bc
> Legal business disclaimers: http://www.CraneSoftwrights.com/legal
>
>
> ---------------------------------------------------------------------
> 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
>
begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services Ltd. email;internet:tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+45 36 95 33 58 tel;cell:+61 438 352228 url:www.documentengineeringservices.com version:2.1 end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]