This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5498 - Use of term 'vacuous'
Summary: Use of term 'vacuous'
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: LC
Assignee: Virginia Smith
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2008-02-20 19:07 UTC by Virginia Smith
Modified: 2008-02-21 22:13 UTC (History)
0 users

See Also:


Attachments

Description Virginia Smith 2008-02-20 19:07:30 UTC
Section 5.1.2 uses the term 'vacuous document' but there is no clear definition of this term. 'Vacuous' could mean absence of content or absence of meaning.

The current text in section 5.1.2 is as follows:

If the model/*/document/data element has no child element, it is said to contain a vacuous document. If the model/*/document/base64Data element has a zero-length sequence of octets as its value, it similarly contains a vacuous document. If a model definition document or an instance document is a vacuous document, then an SML-IF consumer MUST treat the document as if it is not part of the interchange set.

I propose the following text (which removes this term entirely):

If the model/*/document/data element has no child element, then an SML-IF consumer MUST treat the document as if it is not part of the interchange set. If the model/*/document/base64Data element has a zero-length sequence of octets as its value, then an SML-IF consumer MUST treat the document as if it is not part of the interchange set.
Comment 1 Virginia Smith 2008-02-21 19:42:08 UTC
Resolution on 2/21 call - fix per proposal. No needsReview.
Comment 2 Virginia Smith 2008-02-21 22:13:48 UTC
Fixed per proposal.