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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uoml-x message

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


Subject: Re: [uoml-x] Errata Draft submitted for public review


I talked with Mary, and we need only to provide Word and PDF versions of the errata; no need for an ODT version. And it was the ODT version that caused the general issues #3 and #4 described by Mary.

Regards,
Joel Marcey

On Sep 22, 2010, at 2:28 PM, Mary McRae wrote:

> The following changes need to be made to the errata before it can be submitted for public review.
> 
> Change Title to: UOML (Unstructured Operation Markup Language) Part 1 Version 1.0 Draft Errata
> 
> Change Status to: Committee Draft 01
> 
> This Version URIs: The hypertext links behind the text are incorrect and point to erroneous locations
> 
> In general: Please identify section numbers - where sections are removed, replaced, or added in order to know where they should be placed in the resulting document. For instance #4 should say "Editorially Modified the Terminology Clause 1.1 and added new terms"; #5 must give a specific Section # for the new Scope clause, etc.
> 
> In general 2: The descriptions read as if the specification has already been modified. It can't happen that way; the errata is the thing that is approved and once approved is applied to the existing specification. For instance, change "The Font Definition sub-clause was renamed to Font and edited for better clarity." to "Rename/Edit Font Definition sub-clause (Section #) for better clarity"
> 
> In general 3: The items after #6 are no longer numbered. They must be numbered.
> 
> In general 4: I thought that there would be specific references to BRM comment #s and resolutions (in the commented version). The only changes that can be made must be the resulting set of the two organizations' rules: from the OASIS perspective, no substantive changes, from the JTC1 perspective, only those items agreed to at the BRM. Without knowing which issue(s) is addressed with each item I can't ensure that we've done as they have asked.
> 
> The comments below are with regard to specific items although many of the issues are global and need to be corrected before the review can be started.
> 
> Slight Editorial Change to all Normative and Non-Normative References.
> Since you've already repeated the updated Normative References, replace this with the updated Non-Normative ones.
> 
> Uses of docbase, docset and document in paragraph text all become lowercased.
> This is confusing. Does that mean in semantic/property descriptions as well? Needs to be more specific; preferably citing original line numbers.
> 
> Moved all of the UOML objects in Document Architecture (old) to the UOML Objects clause (new).
> Please list all objects, or note that the entire section # was moved to new section #
> 
> The Sub-element items were moved to the new UOML object clause. ??
> 
> Internal Structure of Document sub-clause was removed. Is that a section? a diagram? Need specifics.
> 
> The phrase “Document Global Data” has been removed from the spec. Was it replaced with something else? Unclear. If you just do a search and delete that phrase do the sentences still make sense?
> 
> The Coordinate and Path Encoding Rules sub-clause was moved to the new UOML Objects clause. (and many like this) ... was moved from section #.# to UOML... section #.#
> 
> All Example titles in the UOML Instructions clause were modified. - This one makes no sense to me; particularly when the next item uses the changed format for the before.
> 
> Minor Editorial Changes Were Made Throughout All Instructions. This doesn't explain what the specific changes are. This is the only controlling document; no changes could be made to the Standard based on this statement.
> 
> Consolidated all of the object definitions into a new UOML Objects clause. You moved what to where? What's an object definition? Are they numbered?
> 
> Clearly specified where the normative UOML schema is located. Where will you add this?
> 
> Many editorial changes to the UOML object semantics, properties, etc. Again, the actual text must be incorporated in the errata.
> 
> Added valid ranges and units to the properties of various objects. Where are they in the original spec? What section/sub-section/clause is being modified?
> 
> 
> Regards,
> 
> Mary
> 
> 
> Mary P McRae
> Director, Standards Development
> Technical Committee Administrator
> Member Section Administrator
> OASIS: Advancing open standards for the information society
> email: mary.mcrae@oasis-open.org 
> web: www.oasis-open.org
> twitter: @fiberartisan  #oasisopen
> phone: 1.603.232.9090
> 
> Standards are like parachutes: they work best when they're open.
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 



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