Bridge metadata issue

hi there, i have been using keywords on all my tiffs so far, the recent batch, scanned in using a nikon coolscan v ed 35mm scanner, come in through vuescan (8.4.65) and then into photoshop (cs3) as usual. then i save the tiffs and when i browse in bridge (cs3) i usually right-click and get file info, and then add my keywords. something has changed and the tiffs, when i now right click on them, do not have a file info option. please advise? is there a certain type of file that cannot have metadata? i'm on a macbook pro, os x 10.4.11
thanks
paul

Paul,
What you are seeing is
not normal.
Cache management is the weakest point in Bridge.
Have you purged the cache for the offending folder(s)? DO NOT use the global Purge Cache command in Bridge Preferences because it's broken and the cache does not rebuild properly after using it. Go to the Tools menu in Bridge > Cache

Similar Messages

Custom Info Panel as Bridge MetaData Panel

Hello,
I have built a Custom XMP InfoPanel that shows up in CS6 Bridge just fine! But for ease of data entry we want it to show up in the Bridge MetaData panel. How is this done with the latest best practices?
I have looked everywhere found a number of ways, but ALL are out dated! The XMP FileInfo SDK doesnt cover this.
Thank you
Dean Krueger

Hi Science_DC,
    You are missing the zstring in your label or description and the same issue is with properties too. For testing i changed only two properties but you need to do the smae for others too. I tested after using the ZString and it's working fine in Bridge too. Please find the original and modfied code (only for two properties)
1. Your original properties.xml is
<xmp_schema prefix="custom" namespace="http://my.custom.namespace/" label="<Your label>" description="<Your Panel Description>">
        
        <xmp_property name="Text" category="external" label="<Property Name>" type="text"/>
        <xmp_property name="Text2" category="external" label="<Property Name>" type="text"/>
</xmp_schema>
Insert the ZString like below (inserted text are in bold)
<xmp_schema prefix="custom" namespace="http://my.custom.namespace/" label="$$$/Custom/Panel/Label=<Your label>" description="$$$/Custom/Panel/Description=<Your Panel Description>">
        
        <xmp_property name="Text" category="external" label="$$$/Custom/Panel/Property1 Name=<Property1 Name>" type="text"/>
        <xmp_property name="Text2" category="external" label="$$$/Custom/Panel/Property2 Name=<Property2 Name>" type="text"/>
</xmp_schema>
2. Put that propery file in Custom File Info Panels/4.0/panels (at the same place where DCIM.xml and mobile.xml is)
Following is the screen shot which I got after ZString insertion (CS6 Bridge)
If it doesn't work, could we do remote desktop?
-Sunil

Aperture Metadata and Bridge Metadata

I am a photographer and my workflow is to import all my images into Aperture library and add metadata.
When exporting an image is it possible to integrate Apertures metadata with Bridge metadata? This is important feature as most people do not import images with Aperture. The issue is that many of the field names are different or non existent between the two programs. For example Location field in Bridge is Sub location in Aperture.
Can you add fields such contact info such as URL, email that are included within Bridge ITPC Metadata?
Is there a way to customize the metadata fields to work with CS3?

Unfortunatelly, not really.
I am currently using Nikon Transfer (latest version) to download the pictures from the camera. This software allows me to enter quite a number of IPTC data (including contact information, url, mail, phone, etc.), but maybe not all which are available in CS3.
Then I do import the pictures from the folder into Aperture where I only add contact information in the respective IPTC field. From the tests, I did I do know, that with this step I am using the "old IPTC standard" with Aperture and the new IPTC standard with Nikon Transfer. Clearly the newer is better and meets the needs you described.
In Aperture, I do only see the IPTC data fields, which are common between the two standards (copyright, keywords and description).
When I go to CS3 Bridge, I can see the IPTC data from both, but only of you turn on the "IPTC old" in the Photoshop Bridge settings.
This is how far I have come. I have tested the export with the original and the aperture work copy. As a test reader/viewer of the pics I used Photoshop Elements 5.0 ... but except the copyright information, key words and description, I could not find "my" IPTC data. So there was no contact info. This may be a problem of the old version, so I also checked on a windows PC the file properties (picture viewer), which has more or less the same information.
So the only work around maybe to add contact information into the copyright field - which is not ideal.
Regards
Diethard

Zeiss Otus 1.4/85 ZE not listed in Bridge metadata

The latest release of Camera Raw 8.7 states that the Zeiss Otus 1.4/85 ZE is supported. Whilst in Camera Raw it is listed in the Lens Correction Tab, in Bridge the lens is just described as 85mm in the Metadata section. I also have the Zeiss Otus 1.4/55 ZE lens and this is correctly described in Bridge metadata.
Any ideas why this is would be appreciated - whilst not really an issue it would be nice to have the accurate metadata listed.
I'm running Windows 7 x 64 Pro.
Thanks

Hello,
There are no files like that in that folder (com.apple.safari). They all have long numbers with .jpeg or .png at the end. That's what I meant by I cannot find any files like those mentioned in all the helps I read today. BTW-it's still crashing - no particular pattern to it at all.
The only two things I have downloaded recently is a new version of Flash and a Mac-driven update to Office.
Thank you very much for your attempt to help us.
J.

Metadata issues in A3 - This is a real concern

Metadata issues in A3. This is a real concern if your images go to third parties from A3.
http://www.controlledvocabulary.com/imagedatabases/aperture3.html

Thanks, dzedward,
I posted a reply with quite some effort in it, but it is
dissapeared after pressing the reply button. what I as explaining
was that I use an attached sound and so streaming is not an issue.
Please look at the few lines of code I use in my demo (please use
the link above for the fla with the WAV):
audioClock=new Sound(createEmptyMovieClip("sound1",1));
audioClock.attachSound("theSync");
audioClock.setVolume(90);
stop();
//When playing a swf (in most cases) the audio clock is on
every 46.4399093 ms.
//A onSoundComplete function only starts ON a clock puls!
That explains "gaps"
//when people complain working with audio loops in Flash.
//The audio sample used in this test has a 200 ms duration.
It can't be shorter.
//So it is started 25 ms from the end. When the sample is at
the end, the flash player
//pauses for 46.4399093 minus 25 ms, and starts the audio
sample from the same point
//again ( that is at the next clock puls). That's fine for
hearing audio clock and
//this test:
audioClock.start(0.175,1);
audioClock.onSoundComplete = function() {
audioClock.start(0.175,1);

4.2.1 Does Not Fix" Crash-on-screen saver" bug or metadata issues

ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
You have to set screen saver to "Never" to prevent crashing.
No one checks these things?
Message was edited by: Mike Kwiatkowski

Mike Kwiatkowski wrote:
ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
Metadata issues still hosed.
Not seen the screensaver issue.
Personally I think this update was a patch to fix the DVI flickering issues that rendered the device unusable for many people - other annoyances can be fixed later but we better keep reminding them:
http://www.apple.com/feedback/appletv.html

How to Delete Copyright Status in Bridge Metadata

I have added a copyright status field to bridges metadata by way of a metadata template. How can I delete the status copyrighted. I have made a metadata template with copyright set to unknown, but when I apply it in bridge in does not change the field. Any ideas?
thanks, Joe

This should do it...
#target bridge
   if( BridgeTalk.appName == "bridge" ) {
copyUnknown = MenuElement.create("command", "Copyright to Unknown", "at the end of Thumbnail");
copyUnknown.onSelect = function () {
     copyUnknownSet();
function copyUnknownSet(){
var sels = app.document.selections;
for (var i = 0; i < sels.length; i++){
var md = sels[i].synchronousMetadata;
    md.namespace = "http://ns.adobe.com/xap/1.0/rights/";
    md.Marked = "Unknown";

Metadata Issue iBooks

We recently submitted an Algebra 1 iBook created with iBooks author. Received the message that there was a metadata issue. Was wondering if anyone knew:
1. What is the metadata they are referring to
2. How do you edit it
3. Once fixed, do you have to completely resubmit and start over with the submission process, or can you edit what has already been submitted.
Much thanks

Meta data is the details you entered when you acted to submit your book using iTunes Producer.
Check for red flags for that book in iTunes Producer....could be any number of things - we can't tell without more info
Just edit the stuff for that book using iTP for whatever needs fixing and try again.

Metadata Issue?

I submitted my book Friday morning. Checking yestderday, I see this.
"Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
Trouble is, I can't see anything wrong with the metadata. The blanks are all filled in. Has anyone else seen this? I did a search here and it seems to indicate that Apple won't be able to tell me what the problem is. Any hints or pointers would be greatly appreciated.

It would be easy to verify for iTunes Producer whether the title in the metadata matches the title in the book. Sadly, it doesn't do that.
"Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
Singularly useful error message. The author gets to play the guessing game. Why not just say "The title in the metadata doesn't match the title of the book"?
I have the same problem with many of my submitted ebooks.
All I can suggest is to diligently go through each field of metadata, checking that it meets the requirements set up in the publisher guide and that the metadata is consistent with the book you submitted.
Michi.

Metadata - Issue Can You Customize Apertures Metadata to work with Bridge

I am a photographer and my workflow is to import all my images into Aperture library and add metadata. When exporting image is it possible to integrate the data with Bridge? This is important feature as most people do not import images with Aperture. The issue is that many of the field names are different or non existent between the two programs. For example Location in Bridge is Sub location in Aperture. Can you add contact info such as URL, email that are included within Bridge?
Is there a way to customize the metadata fields to work with CS3?
Any advise is greatly appreciated
Message was edited by: Keith254
Message was edited by: Keith254

Hello Dhruser1,
I think that the DAQmx Perform Bridge Offset Nulling Calibration should work for the SCC-SG24 module. Take a look at this article: Removing Large Initial Offset for Load Cell or Strain Measurements with SCXI-1520 or PXI-4220 in particular it mentions that using this VI in addition to the auto zero can introduce an offset. If you're doing both these is likely the cause.
Also, when you specify specific channels using the channels input are you also setting the "skip unsupported channels to false? If not this may be why it affects other channels.
I hope this helps, and if not please feel free to post back with an update after trying these things.
Cheers,
Brooks

Bridge labels cause metadata issue

It seems when I apply a color label in Bridge to a PSD file (let's say the yellow label, or even a star rating), then open that PSD file... edit it... then save it. I then look at it's metadata in Bridge and notice that the Copyright status went from "unknown" to "public domain." Does anybody know why this is happening?
Even more wacky is when I remove that label and reset the copyright status back to "unknown" in Bridge CS5. I then re-open the PSD file
, make a simple edit, and the save it. The copyright status in Bridge's meta panel goes from "unknown" to "public domain" once again.
I tried this on a friend's computer running CS4, and it does the same thing as well... so it does not seem to be an isolated issue to just my machine.
Thanks

Hi Melissa,
Thanks for your response. I am also noticing that when I create a new PSD CS5 file (let's call it "test.psd"), and then "place" a file that has a label or rating into test.psd, and then save test.psd... Test.psd's copyright status goes from "unknown" to "public domain."
I notice that this situation also happens a lot when I "edit in Photoshop" from Lightroom (when the image in LR has a label or star rating). I always have to check the saved file's meta to see what got messed up, which is really inefficient and cumbersome.
I agree with changing it in File -> File Info, but if I forget to do that every time I open and save this file, it goes back to "public domain." That's a really embarrassing thing for such a robust (expensive) piece of software to not be able to do correctly.
Thank you for responding!

Why does Bridge Metadata Panel look like this...?

I just updated to Photoshop CS6 from CS5.1 and trying to iron out a few issues. One is this...
In Bridge CS 6 my Metadata Panel items are truncated for some reason. There is plenty of room in the panel width, so...? I have even pulled the width out further than shown below. There are no problems with the other panels.
Below are pics of the same panel in my install of CS 6 and then the same panel in my installation of CS 5.1. Thanks.
CS 6 CS 5.1

You've made the headings column too narrow.
Hover your cursor over the space between the 'e' in Fil...e and _IGP1220.DNG. It will change to a resizing indicator, indicating there's a hidden division there. Drag it to the right to make enough room for the headings.
Here's what I see, by the way, when I reduce the UI color to the blackest I can get it in Bridge CS6...
-Noel

MacOS 10.5.4 and Bridge tagging issues

Hi,
My dept just got upgraded to MacOS 10.5.4, and my team is now running into problems tagging PSD files with Bridge (version 2.1.1.9). Upon keying in data in the IPTC fields and applying, I get an error message saying "Error in writing metadata to..." We're attempting to tag these particular files over the network which seems to be the problem since tagging files located on the local system works fine.
So far, all other file formats work fine. It's just PSDs.
And, when we use Photoshop to tag (File Info), it works there. Just seems to be related to Bridge and PSDs over the network.
Any thoughts?
Thanks,
Lisa

This may or may not help with your issue, but you should consider updating your OS to 10.5.5. Some Leopard users have reported increased stability with the latest update.
10.5.4 was bad news. :(

Metadata issue in PPro - UserClipName populates in Metadata and won't go away

I have P2 footage that is behaving oddly in PP - PPro CS6. I am on a PC, using Windows 7 Professional.
Footage was shot and archived onto our PC last summer - as is our typical process - and a PP project was started. It was left dormant till now - 6 months later. I am the new editor tasked with finishing this edit.
I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do). I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields. I saved the project often during this process. I closed the project. I then tried to open another project in PP and nothing opened. I tried to open just the program, and nothing opened. I then logged out of my user account, and then re-logged in. I tried to open PP and it opened fine.
I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it. I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP. I created a new project in PP for the above footage in question, imported it, and there was the UserClipNames in the SHOT metadata field. I did not change any metadata - just saved and closed, and was able to reopen PP. I then tried to add data to the Metadata, save and close - I was not able to reopen PP.
I have imported this footage in various ways - thru the media browser; click and drag from finder window; double click from within the Projects panel then browse to the files; using cntrl-I - and each of these methods was with a clean (new) project. No love.
I also tried to convert this footage directly in Encoder as well as through Prelude (which just takes it to Encoder) into three different formats - P2; Quicktime; H.264 - then created new projects in PP. No love.
What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata. That is a bummer for me - but, oh well. But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully. Fortunately it is only a short PSA, ... and for extra help, I will make my offerings to the Edit-Gods to help get me through to the end without any further issues.
I would love to hear if anyone out here has any suggestions on what might be going on - and ideally a solution. I am okay with appeasing the Edit-Gods - but I would prefer to have more solid solution.
Sali

Hi Sali,
I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do). I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields. I saved the project often during this process. I closed the project. I then tried to open another project in PP and nothing opened. I tried to open just the program, and nothing opened. I then logged out of my user account, and then re-logged in. I tried to open PP and it opened fine.
Thanks for your post.
Let me see if I understand you. You say that the text string, "UserClipName" was in the "Shot" metadata field. By replacing that text string with the a shot number in the Shot metadata you began to have unexpected behavior, such as, not being able to reopen a project. Logging out of your user account, then logging back in allowed you to then open the project. Is that correct? That's pretty odd, for sure.
I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it. I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP.
Sounds like you have hit a bug with P2 footage and Premiere Pro CS6. There is a closed bug in our database, but the state may been triggered with subsequent changes to your system, or the like. The bug also may not have been completely fixed with your particular kind of P2 media.
As I understand it, the issue has to do with how XMP metadata is interpreted by Premiere Pro. I do not believe there is a workaround for this issue other than not changing that particular metadata field. Perhaps you can use a different field, like Comment or Description, for shot number.
What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata. That is a bummer for me - but, oh well. But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully.
I really hope you can get through this project. Let us know if you hit any more issues along the way.
Thanks,
Kevin

Oracle 10g R2 - Metadata Issue With Version Controlled Resources

We are trying to utilize the Oracle 10g R2 feature that allows user-defined metadata to be attached to XML DB resources. However, we are encountering errors when we try to append/attach metadata to a version-controlled resource (VCR). The following steps were followed:
1. Register a new schema to be used for metadata (XMLSCHEMA.registerSchema).
2. Add a new resource to to the XML DB and make it version controlled (DBMS_XDB.createResource and DBMS_XDB_VERSION.makeVersioned).
3. Checkout the newly created version-controlled resource (DBMS_XDB_VERSION.checkout)
4. Add metadata to the version-controlled resource (DBMS_XDB.appendResourceMetadata)
However, after step 4, the errors shown below are encountered:
========================================================
begin
ERROR at line 1:
ORA-00600: internal error code, arguments: [qmxStrCopy: INLOB 2], [], [], [],
ORA-06512: at "XDB.DBMS_XDB", line 890
ORA-06512: at line 2
========================================================
The steps followed for adding metadata to a resource were taken from Chapter 26 of the "Oracle XML DB Developer's Guide 10G Release 2" (http://download-east.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb_repos_meta.htm#sthref2302).
Is is possible to append and maintain metadata to an XML DB version controlled resource (VCR)? If so, what are the correct steps to do this? Note that if this is tried with a resource that is not version controlled, then no errors are encountered.
Thanks,
Steve

It appears that this issue has been solved in the next release of the database
QL> spool testcase.log
SQL> --
SQL> connect &1/&2
Connected.
SQL> --
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> var resourcePath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'metadata.xsd';
3    :schemaPath := '/public/metadata.xsd';
4    :resourcePath := '/public/metadataTest.txt';
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
6          <xs:element name="root" type="rootType" xdb:defaultTable="METADATA_TABLE"/>
7          <xs:complexType name="rootType" xdb:SQLType="METADATA_ROOT_T">
8                  <xs:sequence>
9                          <xs:element name="child" type="childType"/>
10                  </xs:sequence>
11          </xs:complexType>
12          <xs:complexType name="childType" xdb:SQLType="METADATA_CHILD_T">
13                                  <xs:sequence>
14                                          <xs:element name="Child1" type="xs:string"/>
15                                          <xs:element name="Child2" type="xs:string"/>
16                                  </xs:sequence>
17          </xs:complexType>
18 </xs:schema>
19 ');
20 begin
21    if (dbms_xdb.existsResource(:schemaPath)) then
22      dbms_xdb.deleteResource(:schemaPath);
23    end if;
24    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
25 end;
26 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE,
7      enableHierarchy=>DBMS_XMLSCHEMA.ENABLE_HIERARCHY_RESMETADATA
8    );
9 end;
10 /
PL/SQL procedure successfully completed.
SQL> declare
2    res boolean;
3 begin
4    if dbms_xdb.existsResource(:resourcePath) then
5      dbms_xdb.deleteResource(:resourcePath,4);
6    end if;
7    res := dbms_xdb.createResource(:resourcePath,'Mary Had a Little Lamb');
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> select xdbUriType(:resourcePath).getClob()
2 from dual
3 /
XDBURITYPE(:RESOURCEPATH).GETCLOB()
Mary Had a Little Lamb
SQL> declare
2    resid raw(16);
3 begin
4    resid := dbms_xdb_version.makeVersioned(:resourcePath);
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> begin
2    dbms_xdb_version.checkout(:resourcePath);
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> set long 10000 pages 0 lines 150
SQL> --
SQL> select r.res.getClobVal()
2    from resource_view r
3   where equals_path(res,:resourcePath) = 1
4 /
<Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
alid="false" VersionID="1" ActivityID="0" Container="false" CustomRslv="false" V
ersionHistory="false" StickyRef="true">
<CreationDate>2006-06-10T05:01:25.355009</CreationDate>
<ModificationDate>2006-06-10T05:01:25.355009</ModificationDate>
<DisplayName>metadataTest.txt</DisplayName>
<Language>en-US</Language>
<CharacterSet>UTF-8</CharacterSet>
<ContentType>text/plain</ContentType>
<RefCount>1</RefCount>
<ACL>
    <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
//xmlns.oracle.com/xdb/acl.xsd">
      <ace>
        <grant>true</grant>
        <principal>PUBLIC</principal>
        <privilege>
          <all/>
        </privilege>
      </ace>
    </acl>
</ACL>
<Owner>SCOTT</Owner>
<Creator>SCOTT</Creator>
<LastModifier>SCOTT</LastModifier>
<SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#binary</SchemaElement
>
<Contents>
    <text>Mary Had a Little Lamb</text>
</Contents>
<VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
</Resource>
SQL> begin
2    dbms_xdb.appendResourceMetadata(:resourcePath,xmltype(
3 '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
4         xsi:noNamespaceSchemaLocation="metadata.xsd">
5      <child>
6        <Child1>AAA</Child1>
7        <Child2>BBB</Child2>
8      </child>
9 </root>'));
10 end;
11 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> select r.res.getClobVal()
2    from resource_view r
3   where equals_path(res,:resourcePath) = 1
4 /
<Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
alid="false" VersionID="0" ActivityID="0" Container="false" CustomRslv="false" V
ersionHistory="false" StickyRef="true">
<CreationDate>2006-06-10T05:01:25.355009</CreationDate>
<ModificationDate>2006-06-10T05:01:25.558913</ModificationDate>
<DisplayName>metadataTest.txt</DisplayName>
<Language>en-US</Language>
<CharacterSet>UTF-8</CharacterSet>
<ContentType>text/plain</ContentType>
<RefCount>1</RefCount>
<ACL>
    <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
//xmlns.oracle.com/xdb/acl.xsd">
      <ace>
        <grant>true</grant>
        <principal>PUBLIC</principal>
        <privilege>
          <all/>
        </privilege>
      </ace>
    </acl>
</ACL>
<Owner>SCOTT</Owner>
<Creator>SCOTT</Creator>
<LastModifier>SCOTT</LastModifier>
<SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#text</SchemaElement>
<Contents>
    <text>Mary Had a Little Lamb</text>
</Contents>
<VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
<Parents>15DE79F263F8CC00E040578C2A0656F8</Parents>
<root xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNam
espaceSchemaLocation="metadata.xsd">
    <child>
      <Child1>AAA</Child1>
      <Child2>BBB</Child2>
    </child>
</root>
</Resource>
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.0.0 - Alpha
With the Partitioning and Data Mining options
I've filed bug 5313655 for the 10.2.x behavoir. If this is important to you you might want to consider signing up for the forthcoming beta program for the next release of the database

Bridge metadata issue

Similar Messages

Maybe you are looking for