You could do something like that, or:

  Property phone = Contact.PHONE(1,2,2);
  System.out.println(phone.getName()); 
  // -> company[1]/contact[2]/phone[2]

Are these the droids I'm looking for?

  
https://github.com/Gagravarr/VorbisJava/tree/master/tika/src/main/java/org/gagravarr/tika


Regards,

Ray


On August 20, 2014 at 6:25:10 AM, Nick Burch ([email protected]) wrote:
> OK, almost all of it looks fine to me now!
>  
> Taking just one bit:
>  
> > so in your example, setting a value of Audio on two essence tracks would 
> > currently look  
> like:
> >
> > metadata.set(PBCore.ESSENCE_TRACK_TYPE(0), "Audio");
> > metadata.set(PBCore.ESSENCE_TRACK_TYPE(1), "Audio");
> >
> > That index related component could potentially live in the Metadata class 
> > itself but  
> if we choose to support multiple levels of structured properties, i.e.:
> >
> > company[1]/contact[0]/phoneNumber[2]=555-1234
> >
> > that might prove difficult to support.
>  
> Could you nest the property definitions to solve this?
>  
> eg
> Property contact = Contact.COMPANY_CONTACT(1);
> Property phone = Contact.PHONE(contact, 2);
> System.out.println(phone.getName());
> // -> company[1]/contact[2]/phone
>  
>  
> Otherwise, if you promise to help me update the vorbis parsers with
> support for this, I'll vote +1 on adding it in to tika core in this
> form... ;-)
>  
> Nick
>  

Reply via email to