IPTC metadata behavior with faces

With Aperture 3.5.1, a new behavior has been introduced -- writing the name assigned with Faces into the Keywords.
This is problematic because:
1.  It changes the keyword nomenclature and taxonomy
2.  It is not implemented correctly.
1.  I have already established a keyword taxonomy loosely copying the principal of the BDB keyword:value approach.  For example, I have established these keywords:
event
location
family
relative
trip
I then assign keyword to the photo such as:
event:birthday
location:home
family: Mom, family: Dad, family: Bill
Separately of course I can geo-locate the photo, and of course include a caption.  In the case of scanned images, the date may also be modified.
In the past, I have used the 'Write IPTC metadata to original; feature to record this data structure within the IPTC structure.  Then I can search, sort, and organize the photos, within Aperture or in a third party tool.  Some search engines (swish-e for example) can examine IPTC metadata to allow one to automate the searching.  [In fact I wrote a filter to do this for swish-e http://search.cpan.org/dist/SWISH-Filter/lib/SWISH/Filters/IPTC2html.pm#AUTHOR].
With its new behavior, Write IPTC Metadata to Original, now modifies the photo to include additional keywords, not in the keyword HUD or taxonomy, and also adds these new keywords to the Keyword HUD list.
This is problematic because it removes control of the keywords from the archivist and it may expose sensitive information, such as the REAL NAME of an individual identified using Faces.
2.  The names added by this function to the keyword list are incorrect!  In aperture, keywords are separated by commas (',') and then sorted alphabetically (likelyalphanumerically).  However names may contain commas.  For example, I am a "Junior" and I can write my name as 'Bill, Jr' to distinguish myself from my father.  So after writing the IPTC metadata for images that have names assigned, the keyword list is now modified to include 'Bill' and 'Jr.' as new keywords.
Now I understand that IPTC does not include a way of identifying individuals by (x,y) location within the image.  Nevertheless there are conventional ways to write captions (left to right, front to back) to identify all individuals.  There is no need for Aperture to invent a new convention.
Also, this new feature/bug introduces confusion, as searches for my father must now be structured as 'Bill NOT Jr.'  And it add no value to the search process. 
Is there a swtich available in aperture to restore the original behavior, that is, write the keywords that have been assigned and DO NOT make up new keywords?

With its new behavior, Write IPTC Metadata to Original, now modifies the photo to include additional keywords, not in the keyword HUD or taxonomy, and also adds these new keywords to the Keyword HUD list.
Not only with "Write IPTC Metadata to Original", also when exporting a version.
Is there a swtich available in aperture to restore the original behavior, that is, write the keywords that have been assigned and DO NOT make up new keywords?
My experiments have shown (for Faces) that this is toggled by the Aperture Preference "Export > Include Face Information into the exported photos". Try, if disabling this preference will stop this for your library. I have not yet tested the similar option for "Places".
2.  The names added by this function to the keyword list are incorrect!  In aperture, keywords are separated by commas (',') and then sorted alphabetically (likelyalphanumerically).
This is clearly a bug. Submit a bug-report, if you have a Developer account, or use the feedback form:
            Apple - Aperture - Feedback

Similar Messages

  • IPTC Metadata Editor with Spellcheck and more

    Bridge and Lightroom could benefit from a robust metadata editor. Quality IPTC data is almost as important as the images themselves. Afterall that's how we and our clients will find our valuable images.
    Desired Features:
    Spellcheck of at least Description and Keyword fields
    Thesaurus would be great for creating Keyword sets
    More flexible keyword sets to allow more nesting and organizing of similar keywords
    Autofill searching of previously used keywords
    Desired Functionality:
    Must be fast and dependable. Currently Bridge is pretty slow, writing one keyword at a time. This seems to cause Bridge to hang up on itself and spit out corrupt files or not apply metadata to random files among a large selection.
    Perhaps it would be better to have the enter all metadata additions and changes at once to all selected files and hit update, append or replace. FotoStation has had a useful interface in which the user can opt to replace and/or append and/or leave alone various metadata fields all at once.
    Currently it is difficult to resolve a large selection of files that all should have the same keyword(s) but some already have it. We are forced to first remove the keywords(s) by pressing the minus sign, wait for that to happen and then reenter the keyword(s). This can be painfully slow for a large batch of files. I've often resorted to manually writing a metadata template in Wordpad an appending the template. It needs to be easier than that.

    The IPTC metadata needs a large amount of work across all the Adobe product line.
    Desired Functions:
    (1)The identical fields/names and consistent characteristics across all products that generate end-user files; for example, Audition (audio), Acrobat (PDF), Photoshop (image), video products and so on. Audition 1.5 still carries the RIFF metadata but no IPTC format data. Acrobat 7.0.7 Pro does have some IPTC like data fields but has a major data integrity problem with the Description field data. In Photoshop CS2, I can utilize CR/LF via "Enter" to make the presentation more readable as separate paragraphs or new line items. In the Acrobat "Description" field I can follow the same procedure and all looks good upon entry. I do a Save and then bring up the IPTC Description data (same file) and all the data after the first CR (Enter) is lost! Never received any error or warning message.
    (2) I think this pertains mostly to generation of PDF files. Currently, when I generate a PDF document having the same location/file-name that I designate for the "new" file, I appropriately get the warning about the "same name". In addition, give me the option to have the metadata in the "old" file copied to the "new" file.
    (3) Publish (at least in the Help function) all the idiosyncracies for each field (e.g., can I not do CR/LF functions?) and the maximum number of characters possible in each field. Please don't reference me to some standard for the information....tell me what the product line supports! In addition, generate warning messages if I do something outside the field support at the time I am entering data in the field. When possible include such information alongside the field window. One example of this is the note below the keyword window about the comma seperator. The problem with this particular comment is that is states "the comma MAY be used as a separator". Don't tell me what MAY be used...tell me what CAN be used (e.g., spaces, semi-colon, etc.).
    (4) Major update required in the Help function for metadata. Right now it is very poor and not of much use.

  • Writing IPTC Metadata to Masters

    I know some of this has been discussed, but I've got a few more questions on the topic. To ensure my captions, keywords, and location information is always available no matter what cataloging software I use, I wish to write my IPTC metadata to the master images. Here are my concerns:
    1) I have altered the Creator, Headline, Source, Caption, Keywords, Location, City, State/Province, and Country fields - I assume all of these will be written to the masters since they're IPTC standard? Are there length limits for these fields (that is, is there a risk that some will be truncated)? Are there any drawbacks to writing these tags to the masters? (I know many people here don't want their originals touched, but as long as it doesn't affect the quality of my jpegs, I'm fine with it.) Most of my recent photos have GPS metadata - I have not altered these, nor have I added location data to photos that didn't originally have them, so I'm assuming those fields wouldn't be affected?
    2) Is there no IPTC-standard field for people shown in a photo? (I know Aperture/iPhoto's Faces is proprietary, and I'm guessing so is Adobe's People field in their XML metadata.) Should I then just assign people's names as keywords, or is there a better way? (This wouldn't be a problem, as relatively few of my photos have human subjects.)
    3) I have a library of about 45,000 pictures, all of which (except for about 1400 movies) have had some piece of metadata altered. I've noticed Aperture starts to get slow after I've been working in it for a while - so, should I write the tags in stages, or should I just highlight all of them at one time and let it work? About how long should it take?
    4) Finally, I've tested writing the tags to the masters on a few of them, and I've noticed the "date created" shown in the Finder gets changed to the current date and time - Does this mean the entire file was re-created? Would Time Machine have to then re-copy all of them? (My masters total 153 GB, so that might take a while to back up.)
    I know this is a lot at once, but it was a fair amount of work to migrate from iPhoto to Aperture (even with Aperture's convenient import feature) since iPhoto's cataloging tools are different from the IPTC standard. I'm contemplating another migration, and I don't want to have to go through all that again.
    Thanks in advance.

    Thanks all... as I've been digging into this digital asset management concept for a few years now, and there's more to it than I could have imagined!
    viskwal: That's about what I figured. Actually, tagging Faces as keywords will be easy for me since I already have a smart album for each person in Faces. (They're in folders by context - that is, classmate, coworker, family member, etc. - just in case, years down the road, I see a name and don't remember how I know that person.)
    As for locations, I could go back and locate all my photos from before I had the GPS-equipped camera, but I haven't bothered, so I don't know how you'd save that data. I've also been shooting exclusively jpeg since it's got built-in metadata (and I don't do any post-processing), so I have no experience with RAW.
    Michael Hobi: Thanks for the link - I think I'm ok as far as those lengths are concerned. (I have a few long names in the Location field, but that wasn't mentioned there.) As for the write time, that's actually about what I figured - it won't be instantaneous, but at least I'm reasonably sure it won't go on for days. (My original import from iPhoto took 17 hours!)

  • Question Regarding IPTC Metadata

    I've migrated my iPhoto library into Aperture for the expanded geotagging and metadata support, and it was exhausting. (I had Keyword Manager for iPhoto, and Aperture didn't preserve my hierarchy of keywords, though it imported everything else beautifully.) Anyway, I'd like to leave myself open to the possibility of switching to a different program if necessary, so I'm wondering what information would carry over. My questions are as follows:
    1) In the "Write IPTC Metadata to Masters" option, what exactly gets written - I assume everything under the IPTC core, right? (In particular, I've modified the Country/State/City/Location fields, keywords, comments, creator, and source, and it would be a pain to redo all these for 45,000 pictures.)
    2) I presume the aforementioned option only alters the metadata and preserves the original image intact; is this correct? Would there be any repercussions to writing these changes to the masters instead of just keeping them within Aperture's database? It seems a lot of users here insist their originals remain completely untouched.
    3) Is there an IPTC standard for hierarchal keywords, or will I have to recreate the keyword structure in any photo management software I use? (I've experimented with a trial version of Lightroom 3, and I don't even see a way to manage keywords in it...)
    4) Can face tags be written to the metadata? I assume Aperture has its own proprietary format for tagging faces on the photo, but would there at least be an IPTC standard field in which you could list the people tagged in the photo?
    In short, I switched to Aperture because iPhoto's tagging options were inadequate for properly organizing my 45,000 photo library. As I did some research on how to effectively make the transition, I found there was a lot more to this "digital asset management" concept that I realized, and so I'm hoping to get some input from some more experienced users. I'm a real stickler for precision and logic in my organization, and it looks like the IPTC core standard has all the fields I need. Thanks in advance!

    Just another update ... I did some experimenting and found that the "Write IPTC Metadata to Masters" command does at least write the fields I mentioned in the original post. (Those were the only ones I changed on the test photo.)
    Does anyone know offhand if a manually changed date will get written to the master, or will the file still have its original date? (I could test this too, but if someone knows, then I don't have to.)
    Also, most importantly, does the option actually resave the entire master with the updated info, or does it somehow just write the metadata? I ask this because I've read that jpegs lose some data to compression every time they're saved, and I'm wondering if writing those tags will cost the photo some quality.

  • Sort by IPTC Metadata

    Many of my photos were digitized with a slide scanner and I have manually assigned them an IPTC Metadata "date created". In Photoshop Express and Bridge, I can sort by this date, which puts all of my photos automatically in chronological order.
    It seems that Aperature is too antiquated and will only sort by the Exif "image date", which is the date I scanned the slides, and within this date by file name (random). Am I missing something, or is there no way to sort by the "date created?".
    Sad and disappointing if Apple really missed this.

    You seem to be leading with your chin a lot in these posts - luckily for you I've used up my quota of jokes and ripostes for today...
    If you are using referenced mode for your photos, they're right where you left them in the hard disk and you can open them with whatever you like. If they've been actually imported into Aperture's library (ie managed mode) it's possible but not desirable nor recommended.
    If your aperture is suffering from general out of order randomness it sounds like you haven't spent much time setting up the structure to work like you think:
    1. What is your general structure for projects?
    2. Do you use blue folders to group projects (by location, year, client or whatever)
    3. What is your taxonomy for keywording?
    Why would you want to want to try to get to the images directly? Aperture is supposed to hide the anarchy of the way you've stored the photos on the disk and allow you to slice and dice to your heart's content. In starting to use Aperture I changed the project and folder structure in it three times in two months, without ever changing the physical location of the files on the disk. To borrow a phrase from lolcat... "ur doign it wrong"
    Regards,
    Calx

  • Some missing and corrupt IPTC metadata on export

    As a Lightroom user I'm trying Aperture 3, I may be missing something or failing somewhere...
    I've imported some RAW files which already have IPTC metadata, captions, copyright, keywords etc. On export the copyright field has corrupted, the symbol © becomes ¬© and a few fields are missing. I don't have a date, rights usage and the image is marked as unknown copyright status.
    All of that data (except copyright status) appears in Aperture so I'd expect to see it in an exported JPEG. Everything appears as I expect when making a JPEG from Lightroom.
    Thanks for any comments or advice.
    DG

    Novak Yo wrote:
    As a matter of fact, it doesn't export costum filds at all.
    By definition, custom fields are non-standard, and therefore aren't included in the exported file as they won't mean anything to other software. This has been the case since Aperture 1.0 and has absolutely nothing to do with other metadata problems.
    Your website will likely be reading IPTC tags so if you want the information to be readable you'll have to find some appropriate IPTC tags to store the information in.
    Ian

  • Import images WITHOUT any IPTC metadata

    I've been racking by brain trying to work out how to do this, but cannot find a way, I'm sure it's something simple.
    When I import my files the keywords are always imported and put into the top of the keyword directory instead of nested in folders I have organised in the keyword HUD. To solve this I have to remove all the new keywords, then import my IPTC metadata using iView Media Pro and the excellent Annoture.
    Is there a way to import images without any IPTC data coming with them? I have tried 'Add Metadata From: All IPTC' and had it set to replace and left the fields blank, but this did not work.
    Any ideas?

    Ok, half way there. I downloaded an app called Pref Setter to edit the preferences by deleting the array strings that I no longer needed.
    Also you can adjust the hierarchy of the auto completion data. I found that helpful with the copyright field since they all start off the same.
    Need to still find a way to have the data automatically entered from a default setting, with out having to start typing.

  • Moving images from library to library WITH Faces information

    Ok.
    iPhoto 09/faces
    Can someone out there tell me, first off, is it even possible to move photos from one library to another library WITH all the Faces effort I've put in on those photos (say from my default library on my hard drive to another person's library on an external hard drive)?
    That way they don't have to be rescanned and then I have to go through and correct the crappy scanning effort that the program did all over again.
    I tried exporting/importing, straight copy, etc. with no dice.
    I don't want to keep having to re-correct all the faces in images I transfer between libraries.
    "Help me Obi-Wan Kenobi....You're my only hope!"

    For folks out there here is the results of Terrence's suggestion (which was a good one BTW, I don't want to dump on him - it was good thinking on his part! Thanks Terrence).
    iPhoto Lib Manager still ***** (on my system anyway - iMac OSX 10.5.6).
    I installed the thing and tried moving 1000 photos with faces info organized nicely - no dice - it crapped out.
    First make sure all the permissions are set properly and the library mounts automatically (under the options). Then it will at least ATTEMPT to copy everything (also edit prefs to reflect all the metadata that goes with the photos like faces info, dates, desc. etc).
    But while thing appear to go well, it craps out at the end leaving you stymied. It re-scans the imported images and the faces data does not come through in the end despite it's trying to do so.
    I tried it with 80 photos, just to make sure I wasn't trying to fit 20lbs of manure into a 10lb bag. Same story with the smaller transfer
    If I go any smaller, I may as well have used the public version (free) which limits you to 20 at a time.
    So bottom line - according to my experience - if you and someone else have the same photos in your separate libraries and want to share the effort one of you puts into organizing faces info - you're hooped/screwed/pooched!
    Nada - diddly - bupkiss!
    VERY DISAPPOINTING! Both the iPhoto 09 AND the failed (but valiant) attempt by iPhoto Lib Man.
    Should've stuck with iLife 08 and lived with it...sigh.

  • Scripting IPTC metadata in PS CS3

    Has anyone else noticed the following problems when using scripts to manipulate IPTC metadata in Photoshop CS3? Found a way around them?
    --There appears to be no way to access the following fields in a script:
    IPTC Contact: E-Mail(s)
    IPTC Contact: Website(s)
    IPTC Image, Origin: Date Created (N.B. This does not correspond to DocumentInfo.creationDate, for some reason.)
    IPTC Image: Location
    IPTC Status: Rights Usage Terms
    --Whenever I use a script to manipulate the metadata of ANY field (e.g. title, headline, keywords, etc.), any content in the fields listed above is deleted.
    Anyone working on a solution? (That means you, Adobe.)
    Thanks,
    Andrew Slayman

    Paul R.,
    Many thanks for the suggestion. Never used BridgeTalk, so that will take some figuring out.
    But the situation turns out to be more complicated than I thought. Basically, whenever I run a Photoshop action on a batch of PSD images selected in Bridge, it blitzes the five fields listed above. The action needn't have anything to do with metadata, and as far as I can tell the problem affects only PSDs. (DNGs and TIFFs are certainly okay.) So even if I can figure out how to use BridgeTalk, there may be no data for BridgeTalk to retrieve.
    Any idea how one files a bug report around here?
    Andrew

  • Sorting by IPTC Metadata

    Many of my photos were digitized with a slide scanner and I have manually assigned them an IPTC Metadata "date created". In Photoshop Express and Bridge, I can sort by this date, which puts all of my photos automatically in chronological order.
    It seems that Aperature is unable to, and will only sort by the Exif "image date", which is the date I scanned the slides, and within this date by file name (random). Am I missing something, or is there no way to sort by the "date created?".
    I'm talking sorting here, not searching.

    Simply select your pictures, go to the Metadata menu, and choose Adjust date and time. Then EXIF data will be change and will work as expected.

  • Edit IPTC Metadata using Photos?

    I thought Photos was replacing both Aperture and iPhoto.  There appears to be no way to edit IPTC metadata in Photos, which I could do using Aperture.  I consider this to be a serious defect with Photos.

    I thought Photos was replacing both Aperture and iPhoto.
    It's not replacing Aperture. That's now abandoned. If you're a serous Aperture user time to make other arrangements.

  • Returning from a JSF flow with faces-redirect

    I'm using Glassfish 4.1 with JSF 2.2.9. I can't figure out how to return from a JSF flow with a redirect. I've tried this in the flow definition xml:
    <flow-return id="returnFromFlow">
        <from-outcome>/index.xhtml?faces-redirect=true</from-outcome>
    </flow-return>
    This does the redirect but results in navigation errors on the page, specifically the button that enters the flow again: "Unable to find matching navigation case from view ID '/index.xhtml' for outcome 'select-person'" (the flow is called select-person).
    I've also tried appending faces-redirect=true to the action of the commandButton that exits the flow. Now the flow does not exit, it reloads the current page within the flow and says "Unable to find matching navigation case with from-view-id '/select-person/select-person.xhtml' for action 'returnFromFlow?faces-redirect=true' with outcome 'returnFromFlow?faces-redirect=true'"
    Exiting the flow with h:link works, but I want to be able to call an action and submit form values with the button so that isn't a good workaround for me.
    What's kind of interesting is that navigating between views within the flow DOES work with faces-redirect=true. I can add a "step2" node, and a commandButton with action="step2?faces-redirect=true", and it works. It's just exiting the flow that does not work.
    Any ideas?

    Hi Frank,
    Thanks so much for your response.
    Yes, since the user can do a commit prior to exiting my edit task flow, option 1 will not work for me.
    Option 2 sounded feasible, but jdeveloper would not let me set the restore point to true, since my btf didn't require a transaction. Is there a step I'm missing here??
    The thing that is really getting me when return via the cancel button from this edit task flow, back to my parent task flow, the record pointer is always moving back to the beginning of the data set in my parent task flow. For example,if I have a data set
    rec1, rec2, rec3..
    On my parent taskflow call it browser task flow, I navigate (via the next button) to rec3, and I click edit. At this point, my edit task flow kicks off, and since both task flows share the same data control, the edit task flow rec pointer is the same as the browse one.
    Okay I decide I don't want to change anything in my rec3, so I click cancel.
    At this point, when I return back to the navigator task flow, it points me back to rec1 ..
    HOwever, the savepoint seems to fix this. When I set my cancel return from edit taskflow to savePoint = true, the rec pointer stays in the correct spot. However, I cannot always do this, because the user can make iterative saves in the edit task flow which (based on your previous email) stales out the savepoint id.
    Question, so in this case, how can I make the parent browser task flow call stay on the same record I was just editing, opposed to going back to the beginning of the data set(ie. rec1)??

  • Face time fades out and then tries to reconnect on new ipad retina display on WiFi.  Iphone 4s has no problem with face time from exact same location and same contact.  WiFi signal strong on both devices.  What gives?

    Face time fades out and then retries to connect (new Ipad Retina Display) on WiFi. Iphone 4s has no problem with face time from same location and same contact.  What gives?

    rdallas001 wrote:
    Is the router to small?
    Not necessarily, if you are using Facetime all the data goes through your WiFi router, your cable/DSL modem, your ISP and the internet to Apple's Facetime servers and then, in reverse, down to the Facetime recipient. If your ISP connection is too slow or there is excessive traffic on the internet you can have Facetime problems.
    Most WiFi routers can handle this unless others in the house are also using WiFi at the same time. The problem may be your ISP connection or congestion on the internet, etc.

  • Erratic Report Region Behavior with Dynamic SQL Queries

    I'm running HTMLDB v 1.5.1.00.12 and I've noticed some odd behavior with report regions using dynamic SQL queries. Every so often, our testers will run a page containing a dynamic sql report region and get the following error, (despite the fact the query was working only moments ago and no other developer has touched it):
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    or sometimes
    failed to parse SQL query:ORA-01403: no data found
    The only solution I've found so far is to:
    1) Make a copy of the failed report region.
    2) Disable or delete the original failed report region.
    The new copy of the report region runs without issue.
    My search of the forums turned up the following two threads, but neither provided me with a clear explanation of the cause, and how to avoid it:
    ORA-06502:PL/SQL: numeric or value error: character string buffer too small
    Re: Import Export Error (ORA-06502)
    The columns being returned are below the 4000 character limit, and the rows being returned are far less than 32k in size.
    Could this have anything to do with the way HTMLDB is internally storing the PL/SQL used to generate the dynamic SQL Query? Is there any known issue related to this with that version of HTMLDB?
    This problem occurs without any discernable pattern or consistency, making it hard to determine where I should focus my efforts in tracking down the cause.

    Hi all,
    My report seems to be behaving correctly once i set it to "Use Generic Column Names (parse query at runtime only)" :)
    Cheers,
    Joel

  • Problem w.r.t. JSF 2.0 with faces-config.xml

    Hi All,
    I am trying to evaluate the features of JSF2.0.
    For that, I have created a very simple application with "JSF 2.0.2".
    There is a page that displays a composite component and some other form related components (inputtext, commandbutton).
    When I deploy my application without any faces-config.xml file, everything renders perfectly fine.
    When I deploy the app with faces-config.xml (even an empty one without any configuration), none of the components get rendered.
    Only the html elements get displayed.
    I need to define some navigation-rules in my config file. I am not sure how to go further from here.
    The app server I am using for deploying my app is GlassFish(v3).
    Any help or pointers towards solving my problem are highly appreciated.
    You can find the xhtml file, etc of my project below.
    Thank you,
    With best regards,
    Praveen
    web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5">
         <context-param>
              <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
              <param-value>.xhtml</param-value>
         </context-param>
         <servlet>
              <servlet-name>Faces Servlet</servlet-name>
              <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>*.jsf</url-pattern>
         </servlet-mapping>
    </web-app>
    faces-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config xmlns="http://java.sun.com/JSF/Configuration">
    </faces-config>
    resources->acicomp->namesection.xhtml
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
          xmlns:ui="http://java.sun.com/jsf/facelets"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:composite="http://java.sun.com/jsf/composite">
    <composite:interface>
    </composite:interface>
    <composite:implementation>
         <h:panelGroup>
         <h:panelGrid columns="2">
              <h:outputText value="Name: "/>
              <h:inputText value="myName"/>
              <h:outputText value="Company: "/>
              <h:inputText value="myComp"/>
         </h:panelGrid>
         </h:panelGroup>
    </composite:implementation>
    </html>
    index.xhtml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:aci="http://java.sun.com/jsf/composite/acicomp">
    <h:head>
         <title>JSF Test Program</title>
    </h:head>
    <h:body>
         <p>My Simple Test Program</p>
            <h:form id="testForm" >
                <p>TEST</p>
                <aci:namesection></aci:namesection>
                <h:inputText id="username" value="John" />
                <h:commandButton id="submit" action="response" value="Submit"/>
            </h:form>
    </h:body>
    </html>

    I found the problem.
    The dtd location of the faces-config.xml had to be changed. It was pointing to the schema of 1.1.
    With the following faces-config.xml, my application worked perfectly fine.
    <?xml version="1.0"?>
    <faces-config xmlns="http://java.sun.com/xml/ns/javaee"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
                  version="2.0">             
    </faces-config>

Maybe you are looking for