[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-174) Experimental extensible ABIEs
[ https://issues.oasis-open.org/browse/UBL-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69245#comment-69245 ] Roberto Cisternino edited comment on UBL-174 at 3/4/18 6:35 AM: ---------------------------------------------------------------- About adding an extension point at the beginning of *every* ABIE I would like to send my comments and contribution. Firstly I do not think that the requirement of having an extension point on every ABIE is to create complex data structures, but simple information items on that context. I also think that these small extension points should reference a document-level UBLExtension that should act as the main extension definition (e.g. for accounting purposes) I now start calling this context-driven extension a LocalExtension, but it is just an example. I would leave extensions based on other non-UBL namespaces at document-level using the actual UBLExtension, so I skipped this aspect here. I drafted this LocalExtension as a very generic and simple business information extension as follows: ## LocalExtension [0..n] * ID [0..1] An identifier for the Local Extension assigned by the creator of the extension. * DocumentExtensionID [1..1] An identifier to reference the Document-level Extension driving this Local Extension. * ExtensionName [1..1] A meaninful business term describing this Local Extension. * ExtensionTypeCode [0..1] A code for the type of Local Extension. * Date [0..1] A date value that may be required by this Extension. * Time [0..1] A time or duration value that may be required by this Extension. * Identifier [0..1] An identifier that may be required by this Extension. * Indicator [0..1] An indicator that may be required by this Extension. * Percent [0..1] A percent value that may be required by this Extension. * Amount [0..1] An amount value that may be required by this Extension. * Quantity [0..1] A quantity value that may be required by this Extension. * Measure [0..1] A measure value that may be required by this Extension. * Text [0..1] A textual value that may be required by this Extension. * DocumentReference [0..1] A document reference that may be required by this Extension. I intentionally avoided to add a Binary Object but could be added for completeness. I would not add other specific ABIEs because I think this kind of LocalExtension must be used to add simple information. was (Author: r0bert0): About adding an extension point at the beginning of *every* ABIE I would like to send my comments and contribution. Firstly I do not think that the requirement of having an extension point on every ABIE is to create complex data structures, but simple information items on that context. I also think that these small extension points should reference a document-level UBLExtension that should act as the main extension definition (e.g. for accounting purposes) I now start calling this context-driven extension a LocalExtension, but it is just an example. I would leave extensions based on other non-UBL namespaces at document-level using the actual UBLExtension, so I skipped this aspect here. I drafted this LocalExtension as a very generic and simple business information extension as follows: h2. LocalExtension [0..n] * ID [0..1] An identifier for the Local Extension assigned by the creator of the extension. * DocumentExtensionID [1..1] An identifier to reference the Document-level Extension driving this Local Extension. * ExtensionName [1..1] A meaninful business term describing this Local Extension. * ExtensionTypeCode [0..1] A code for the type of Local Extension. * Date [0..1] A date value that may be required by this Extension. * Time [0..1] A time or duration value that may be required by this Extension. * Identifier [0..1] An identifier that may be required by this Extension. * Indicator [0..1] An indicator that may be required by this Extension. * Percent [0..1] A percent value that may be required by this Extension. * Amount [0..1] An amount value that may be required by this Extension. * Quantity [0..1] A quantity value that may be required by this Extension. * Measure [0..1] A measure value that may be required by this Extension. * Text [0..1] A textual value that may be required by this Extension. * DocumentReference [0..1] A document reference that may be required by this Extension. I intentionally avoided to add a Binary Object but could be added for completeness. I would not add other specific ABIEs because I think this kind of LocalExtension must be used to add simple information. > Experimental extensible ABIEs > ----------------------------- > > Key: UBL-174 > URL: https://issues.oasis-open.org/browse/UBL-174 > Project: OASIS Universal Business Language (UBL) TC > Issue Type: New Feature > Components: Naming and Design Rules (NDR) > Reporter: Ken Holman > Assignee: Ken Holman > Priority: Minor > > A set of UBL 2.1 schemas with individually extensible ABIEs is found here: > https://www.oasis-open.org/committees/document.php?document_id=62585 > In the "val/" directory you will find order-test-good.xml that has a custom extension at the line item level. Running "test.bat" or "sh test.sh" validates the document. > The "xsd/" and "xsdrt/" are as expected, except that the Aggregates fragment now allows <ext:UBLExtensions> on every ABIE. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]