bon bon, are you looking for who the copyright holders are for those particular works?
Zoe ,'Serenity'
Buffistechnology 3: "Press Some Buttons, See What Happens."
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
bon bon, are you looking for who the copyright holders are for those particular works?
Yeah, and the years, but at this point I'm only looking for xpparse2.c and xpyaxx.tab.c, which are apparently Skeleton output parsers for bison, whatever that means.
I'm only looking for xpparse2.c and xpyaxx.tab.c, which are apparently Skeleton output parsers for bison, whatever that means.
It means that those two files weren't directly written by a human, they were generated by a program called bison, from a higher-level source file.
Bison is a type of program called a "parser generator", which takes code that describes the grammar of a programming language, and outputs a program that will parse the grammar.
The source file(s) that generated those xp*.c files would have a .y extension, perhaps xpparse.y and xpyacc.y
If generated that way, I wonder if they can be copyrighted. My problem in doing this is I don't have the software, I just have a list of third party software that's in it, and I am trying to make the correct copyright disclosures for that software.
The GPL has specific language that covers "derivative works", which would apply in these circumstances.
I am extremely familiar with the licenses; I am just having trouble finding the actual text of the copyright -- as in, "The Remote Tea Java Package has been written by Harald Albrecht (harald@plt.rwth-aachen.de). Copyright © 1999, 2003 Chair of Process Control Engineering,Aachen University of Technology,52064 Aachen, Germany." That language.
But do you need to disclose the copyrights of software that you are using with via the GPL? If so, it would seem to make it prohibitively hard to release anything that used GPL'd software.
I would be curious to know what is prohibitive. My understanding is that -- leaving the viral problem aside-- you just need to keep all notices intact and have a copy of the license and a disclosure of who owns the copyright and what years where the user will find it (the readme, or the help section under legal disclosures, for example). Also make the source code available. (I want to type more but this keyboard is giving me trouble!)
Well, imagine you want to ship a product with Ubuntu Linux installed. How are you ever going to find who owns the copyright every piece of source code included in building the distribution?
Here's a question for the hivemind - is there any podcast creation software out there that will let me customize the XML it generates? Or an XML editor that will do this for me?
Basically, I need to generate NITF documents to assign metadata to a large number of video files, and I don't want to have to type each one out individually because it will take an assload of time. (We're talking 500+ videos.) And so far all the podcasting software I've looked at generates XML with itunes-specific tags.