Re: [tab] Re: [ubl-comment] UBL Naming and Design Rules Version 3.0

[Patrick Durusau <patrick@durusau.net>]

Ken,

Great!

So, looking at

3 Documents, libraries, components and extensions is:

****

These naming and design rules provide for creating a collection of 
extensible documents. Each document is an information bundle of business 
information entities sharing one or more common libraries of business 
information entities. Each business information entity is referred to as 
a component of the information bundle of the document or library. Each 
component corresponds to an XML element.

A document extension provides for content that augments an information 
bundle with additional information not previously defined for the 
information bundle. Extensions, themselves, can contain components and 
can reference components. Extensions can also include foreign constructs 
defined by other organizations not using CCTS for structuring 
information. An extension can have horizontal applicability to all 
documents, such as the scaffolding to house a digital signature. An 
extension can have vertical applicability to only a single document, 
such as additional invoice line detail information to augment an invoice 
for a specific industry.

Each exchange between partners is realized as a machine-readable 
instance of the information bundle and its use of any common libraries. 
When using XML for exchange, the XML document presents the information 
bundle as a serialization of components, each component being an XML 
element. Extensions in XML documents provide for including XML elements 
of components or of other XML vocabularies.

****

normative or non-normative?

It falls neither under the first sub-section nor under the second 
sub-section, but is in fact a collection of hanging paragraphs.

That is if I refer to 3 Documents, libraries, components and extensions, 
do I mean just the three paragraphs I quoted above or do I mean all of 
section 3?

Personally I would insert 3.1 (and sections under the other main 
sections as necessary) to hold these paragraphs and say that everything 
that isn't a note or marked non-normative is normative. Rather than 
relying on readers to understand that normative or non-normative is 
implied by the earlier description.

Hope you are having a great day!

Patrick

On 04/28/2015 05:40 PM, G. Ken Holman wrote:
> At 2015-04-28 17:01 -0400, Patrick Durusau wrote:
> > https://issues.oasis-open.org/browse/TAB-1141
> >
> > is about as inelegant as is possible in English prose! Sorry! I will 
> > try to clarify.
> >
> > I read the documentation conventions to mean:
> >
> > All *.1 subclauses are normative. (normative prescriptive rules in 
> > the first subclause)
> >
> > All *.2 subclauses are non-normative. (non-normative UBL 2.13 
> > Documents, libraries, components and extensions application of those 
> > rules in the second subclause.)
> >
> > Yes?
>
> Yes!
>
> And I understand that the declared non-normative stature of clause 3.2 
> is inherited by subclauses 3.2.1 through 3.2.4.  If such inheritance 
> is not implied, then absolutely the editors are obliged to go in and 
> declare the non-normative stature of those subclauses.  But if the 
> inheritance is implied then I think it unnecessary to duplicate the 
> declarations.
>
> > If we are missing each other on that point, let me know so we can get 
> > together there before I go any further.
> >
> > Hope the comments were helpful!
>
> Absolutely, yes, and I hope you know how appreciative we are of your 
> efforts.
>
> . . . . . . . . Ken
>
>
> --
> Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
> Free 5-hour lecture: http://www.CraneSoftwrights.com/links/video.htm |
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ |
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com |
> Google+ profile: http://plus.google.com/+GKenHolman-Crane/about |
> Legal business disclaimers: http://www.CraneSoftwrights.com/legal |
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
>
> ---------------------------------------------------------------------
> 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