When the PREMIS Data Dictionary was developed, it was thought that
eventOutcomeDetail might need some additional structure, which might be
done locally, but that structure wasn't specified. I think that is why the
schema is written this way, although the entry in the data dictionary
itself doesn't say that it must have children. In any case, we are almost
finished with the revision of the data dictionary and this is one case
where we are allowing extensibility for any additional structure that is
needed. So we are adding a container unit to include either
eventOutcomeDetail, which would contain unstructured text, and/or an
extension element, which may have additional structure, locally defined or
from another schema.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior Networking and Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ 1st and Independence Ave. SE ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4402 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ [log in to unmask] ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Thu, 31 Jan 2008, Euan Cochrane wrote:
> Hi Bill,
>
> I think the problem is that the <eventOutcomeDetail> element cannot have
> any information stored directly inside of it. It needs to have a child
> element (any element- you can make one up-) inserted into it.
> For example:
>
> <eventOutcomeDetail>
> <notes>These are the details about the event</notes
> </eventOutcomeDetail>
>
> I am not sure why this is, but it seems to make the files valid.
>
> Cheers,
>
> Euan Cochrane
>
> Statistical Analyst,
> Information Management
> Statistics New Zealand
> [log in to unmask]
> +64 (0)4 9314371
>
>
>
> Bill Walker <[log in to unmask]>
> Sent by: PREMIS Implementors Group Forum <[log in to unmask]>
> 31/01/2008 09:58 AM
> Please respond to
> PREMIS Implementors Group Forum <[log in to unmask]>
>
>
> To
> [log in to unmask]
> cc
>
> Subject
> [PIG] PREMIS Event Problem
>
>
>
>
>
>
> I am having a problem with an <eventOutcomeDetail> element in a PREMIS
> event.
>
> Here is my event:
>
> <event xmlns="http://www.loc.gov/standards/premis/v1"
> xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="
> http://www.loc.gov/standards/premis/v1
> http://www.loc.gov/standards/premis/v1/Event-v1-1.xsd">
> <eventIdentifier>
> <eventIdentifierType>local
> </eventIdentifierType>
> <eventIdentifierValue>test
> </eventIdentifierValue>
> </eventIdentifier>
> <eventType>File Conversion</eventType>
> <eventDateTime>2008-01-10T10:25:52-06:00
> </eventDateTime>
> <eventDetail>Converted 6 files from TIFF to JPEG
> Thumbnails</eventDetail>
> <eventOutcomeInformation>
> <eventOutcome>Success</eventOutcome>
> <eventOutcomeDetail>Well-Formed and valid
> </eventOutcomeDetail>
> </eventOutcomeInformation>
> <linkingAgentIdentifier>
> <linkingAgentIdentifierType>Creator
> </linkingAgentIdentifierType>
> <linkingAgentIdentifierValue>Bill Walker
> </linkingAgentIdentifierValue>
> </linkingAgentIdentifier>
> </event>
>
> An example PREMIS event from the Library of Congress has the following:
>
> <premis:event>
> <premis:eventIdentifier>
> <premis:eventIdentifierType>LocalRepository
> </premis:eventIdentifierType>
> <premis:eventIdentifierValue>e001.1</premis:eventIdentifierValue>
> </premis:eventIdentifier>
> <premis:eventType>validation</premis:eventType>
> <premis:eventDateTime>2006-06-06T00:00:00.001</premis:eventDateTime>
> <premis:eventDetail>jhove1_1e</premis:eventDetail>
> <premis:eventOutcomeInformation>
> <premis:eventOutcome>successful</premis:eventOutcome>
> <premis:eventOutcomeDetail>Well-formed and valid
> </premis:eventOutcomeDetail>
> </premis:eventOutcomeInformation>
> <premis:linkingAgentIdentifier>
> <premis:linkingAgentIdentifierType>AgentID
> </premis:linkingAgentIdentifierType>
> <premis:linkingAgentIdentifierValue>na12345
> </premis:linkingAgentIdentifierValue>
> </premis:linkingAgentIdentifier>
> <premis:linkingObjectIdentifier>
> <premis:linkingObjectIdentifierType>hdl
> </premis:linkingObjectIdentifierType>
> <premis:linkingObjectIdentifierValue>
> loc.music/gottlieb.09601
> </premis:linkingObjectIdentifierValue>
> </premis:linkingObjectIdentifier>
> </premis:event>
>
> The error I get in Oxygen is: Element 'eventOutcomeDetail' cannot have
> character [children], because the type's content type is element-only.
> But when I look at the Schema and see what elements are available, there
> are none.
>
> The relevant part of the schema is this (I think):
>
> <xs:element name="eventDetail" type="xs:string" minOccurs="0"/>
> <xs:element name="eventOutcomeInformation" minOccurs="0"
> maxOccurs="unbounded">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="eventOutcome"
> type="xs:string" minOccurs="0"/>
> <xs:element
> name="eventOutcomeDetail" minOccurs="0">
> <xs:complexType>
> <xs:sequence>
> <xs:any namespace="##any" processContents="lax"/>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> What does ?<xs:any namespace="##any" processContents="lax"/>? mean and
> what can I put inside this field?
>
> Thanks,
>
>
> =========================================
> Bill Walker
> Imaging Field Services Officer
> Amigos Library Services,
> 14400 Midway Road, Dallas, TX 75244-3509
> 800-843-8482 x2853
> 972-340-2853 (direct)
> 972-991-6061 (fax)
> www.amigos.org Email: [log in to unmask]
> =========================================
>
>
> The first source of independent information for your key decisions
>
> ====================== Correspondents: Please Note =====================
> The information in this email, and any files transmitted with it, is
> confidential and is for the intended recipient only. If you receive
> this message in error, please phone us toll free on 0508 525 525, or
> notify us via [log in to unmask]
>
> The content of any email entering or leaving Statistics New Zealand is
> automatically scanned, and may be opened and read by security staff.
>
> Statistics New Zealand makes reasonable efforts to ensure that its email
> has been scanned and is free of viruses. However, Statistics New Zealand
> can make no warranty that this email or any attachments to it are free
> from viruses.
> ========================================================================
>
>
>
|