LISTSERV mailing list manager LISTSERV 16.0

Help for MIX Archives


MIX Archives

MIX Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MIX Home

MIX Home

MIX  March 2007

MIX March 2007

Subject:

Re: BitsPerSample question

From:

"Morgan V. Cundiff" <[log in to unmask]>

Reply-To:

NISO Metadata for Images in XML (MIX)

Date:

Mon, 19 Mar 2007 10:17:20 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (58 lines)

Regarding optional/mandatory discrepancies between Data Dictionary and MIX
1.0- there were two reasons for this:

- the DD specifies many mandatory elements. The experience of the
implementors of the earlier version of MIX was that they could not in
practice comply with so many mandatory elements but still wanted to use
MIX to provide the data they could capture. The assumption here is that
still holds true.

- the DD specifies that some elements are conditionally mandatory
(e.g. element foo is mandatory if the value of element bar is x. XML
Schema does not accomodate this very well and so it seemed another reason
to not attempt make the schema follow the data dictionary in that regard.



Morgan Cundiff


On Sun, 18 Mar 2007, Gary McGath wrote:

> [log in to unmask] wrote:
> > Hi Gary,
> > 
> > I'm looking at the ANSI/NISO Z39.87-2006 document. There (on pp.  
> > 76-78), it states that these two data elements (bitsPerSampleValue and  
> > bitsPerSampleUnit are mandatory, not optional.
> 
> Then there's a disagreement between the data dictionary and the schema. 
> All of these elements in the schema have minOccurs="0", which makes them 
> optional.
> 
> > What may be confusing about bitsPerSampleUnit is that it really  
> > specifies how the bits are to be interpreted, as "integer" or as  
> > "floating point."
> > 
> > To answer your question, based on the NISO document's examples, for  
> > 24-bit RGB:
> > bitsPerSampleValue = 8,8,8
> > bitsPerSampleUnit = integer
> 
> Well, OK, but that's counterintuitive at least. "8,8,8" is not what 
> anyone would consider an "integer" value. I hope documentation will be 
> forthcoming to explain this. The encoding of multiple values as a 
> comma-separated string isn't great XML practice, but I guess we'll have 
> to live with it.
> 
> 
> > Hope this was helpful,
> 
> Thanks.
> 
> -- 
> Gary McGath
> Digital Library Software Engineer
> Harvard University Libraries, Office for Information Systems
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2018
July 2017
June 2017
July 2016
June 2016
May 2016
April 2016
May 2015
March 2015
July 2014
June 2014
May 2014
April 2014
June 2013
May 2013
May 2012
April 2012
March 2012
June 2010
April 2010
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
September 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
August 2007
May 2007
March 2007
February 2007
November 2006
July 2006
April 2006
January 2006
September 2005
April 2005
February 2005
September 2004
August 2004
April 2004
February 2004
June 2003
May 2003
April 2003
November 2002
May 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager